Determine whether a San Francisco building project falls under Planning Code Section 139 bird-safe glazing standards and what glazing treatment satisfies it.
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pull San Francisco Planning Code Section 139 'Standards for Bird-Safe Buildings' via the official amlegal.com code library mirror or sfplanning.org
Identify which of the two hazard types applies: location-related hazard (site within 300 feet of an Urban Bird Refuge) or feature-related hazard (free-standing glass walls, wind barriers, skywalks, balconies, or rooftop greenhouses with unbroken glazed segments 24 sq ft or larger)
Confirm applicability triggers: new construction, an addition that creates a bird hazard, or replacement of 50% or more of the glazing on an existing bird-hazard condition
Review acceptable Bird-Safe Glazing Treatments: fritting, netting, permanent stencils, frosted glass, exterior screens, physical grids, or UV patterns visible to birds, meeting the pattern-density spec (vertical elements ≥1/4 in. wide at ≤4 in. spacing, or horizontal elements ≥1/8 in. wide at ≤2 in. spacing)
Consult sfplanning.org's published Design Guide for Standards for Bird-Safe Buildings for illustrated compliance examples before finalizing a glazing product selection
Known gotchas
San Francisco's triggers and thresholds (300-ft refuge radius, 24-sq-ft unbroken segment, 50% replacement threshold) are specific to this ordinance and differ from NYC LL15's height-based (75-ft) and percentage (10 sq ft/100 sq ft) framework — the two cities' rules are not interchangeable
The pattern-density spacing spec (1/4 in./4 in. or 1/8 in./2 in.) is a precise technical requirement; a fritted glass product must be verified against these exact dimensions, not just marketed generically as 'bird-friendly'
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?