nyc-mesh

What It Is

nyc-mesh bridges raw NYC 3D releases (CityGML, LiDAR, DEMs, footprints) and practical outputs for browsers, notebooks, and reproducible analysis. The goal is a short path from “point at official source data” to clipped buildings, joined attributes, terrain meshes, and web-friendly exports.

Why It Exists

The City publishes rich 3D data, but the files are large, specialist, and painful to turn into something you can render or analyze at neighborhood scale. This package packages the opinionated first workflow: reproject, clip, join context, export.

What Ships Today

• Load local or zip-wrapped CityGML, LiDAR, DEM, and footprint inputs; large archives stay as local cache, not in git
• Fetch PLUTO and building-footprint context for a study-area bounding box
• Reproject source coordinates from EPSG:2263 to EPSG:4326; clip to named study areas or explicit WGS84 boxes
• Join PLUTO-style attributes onto extracted buildings (workflow focuses on buildings that expose bldg:measuredHeight)
• Generate lightweight terrain meshes from DEM or LiDAR
• Export GeoJSON, GeoParquet, glTF, and a minimal 3D Tiles bundle; build typed cache manifests
• CLI such as nyc-mesh export-geojson plus pipeline helpers in the nyc_mesh package

Self-contained examples under examples/ mirror the pattern used in nyc311 (per-folder pyproject.toml, README, and runnable outputs)—see quickstart-citygml, landmark-3d-stack, building-height-analysis, and the shared example-template.

Ecosystem Fit

Complements the 2D boundary stack in nyc-geo-toolkit and the tabular or service-request workflows in nyc311: here the emphasis is NYC’s 3D corpus and web-ready geometry rather than complaints or administrative polygons alone.