portolan-pipeline
Boston's official open space inventory, valuable and messy in the way municipal GIS data actually is. No stable key, free-text code columns, and sentinel strings. The quirks below are each verified against the data and each prevents a silently wrong answer.
Query the GeoParquet data asset in place with DuckDB spatial, read_parquet('boston-open-space.parquet'), or load it with GeoPandas. It streams over HTTP range requests, so query the published URL directly rather than downloading first. For rendering use the visual PMTiles asset with its MapLibre styles.
Geometry is WGS84 degrees, so ST_Area returns square degrees. The
official ACRES column matches geodesic geometry area to a median of
0.003 acres, use it. If you must compute, DuckDB's spheroid function
wants latitude first, and skipping the flip shrinks Boston by more
than half.
Eighteen sites disagree with their geometry by more than 10 percent, documented cases like Condor Street Overlook where ACRES excludes mudflats the polygon includes.
Acreage by normalized type.
Which open space contains a point. Boston Common from its center.
Protected share by district.
boundaries/us-counties contains Boston at a far coarser scale, and a
spatial join is the only bridge. The upstream layer on Analyze Boston
is continuously maintained and now carries columns this July 2026
snapshot predates, OS_ID, ZipCode, ParcelNumber, YearAcquired.
Converted from the city's Shapefile export with DuckDB spatial into
web-optimized GeoParquet 2.0.