Forestry Planting Spaces

March 2021 Geographic Difficulty 3/5 CSV 115.7 MB 985,278 rows × 35 cols 0 downloads
  • forestry
  • nyc
  • urban-planning
  • geographic
  • civic

985,278 NYC planting-space records with borough, street, council district, and size fields. Supports urban-planning dashboards, geospatial mapping, and community-board-level green-space analysis.

Challenge brief


slug: 2021-03-forestry-planting-spaces title: Forestry Planting Spaces year: 2021 month: 03 source: authored authored_at: 2026-04-19 needs_leon_review: true

Forestry Planting Spaces - Challenge Brief

Challenge period: March 2021 Dataset: Reconstructed brief based on the shipped data file for the March 2021 DataDNA challenge.

About the data

The primary data table for this challenge carries the following columns:

  • OBJECTID
  • Borough
  • Number
  • Street
  • PSSite
  • PlantingSpaceOnStreet
  • Width
  • Length
  • ParkName
  • ParkZone
  • CrossStreet1
  • CrossStreet2
  • CommunityBoard
  • SanitationZone
  • Postcode
  • Council District
  • StateSenate
  • StateAssembly
  • Congressional
  • PhysicalID
  • PSStatus
  • Geometry
  • GlobalID
  • CreatedDate
  • UpdatedDate
  • ...and 10 more columns

Suggested analytical angles

  • Which boroughs and council districts have the most planting spaces available?
  • How do widths and lengths of spaces vary across NYC?
  • Where are overhead utilities most likely to constrain planting decisions?
  • Which community boards have the highest unplanted stock?

What great submissions did

This brief was reconstructed from the dataset contents in 2026 as part of the Playground audit. The original March 2021 challenge brief was not preserved as a separate file in the source archive, so the analytical angles above are inferred from the column list. See the corresponding /challenges/ entry on datadna.onyxdata.co.uk for examples of how participants approached the data.

Editorial note

_This stub was authored by Claude on 2026-04-19 for Leon's review. Refine the suggested angles and confirm factual accuracy before setting brief_status = leon_reviewed in the audit log._

Browse open challenges