Ensure an illuminated sign complies with light-trespass / dark-sky ordinance requirements
domain: darksky.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify whether the local jurisdiction has adopted a dark-sky or outdoor-lighting ordinance (often modeled on frameworks published by dark-sky advocacy organizations) separate from its general sign code
Confirm shielding/cutoff requirements for the sign's light source so illumination is directed onto the sign face rather than spilling upward or onto adjacent properties
Confirm any maximum illuminance/light-trespass limit measured at the property line and any curfew/shutoff hours that apply to illuminated or internally lit signs specifically, not just to general site lighting
Check for color-temperature or lumen-output caps that some dark-sky ordinances apply to sign lighting in addition to general fixtures
Coordinate the sign's photometric plan with whatever documentation the ordinance requires (e.g., a light-trespass calculation) as part of the permit submittal
Known gotchas
Dark-sky/light-trespass rules are frequently enforced through a separate lighting ordinance from the sign ordinance — clearing sign-area and height rules does not guarantee lighting compliance
Requirements (shielding, curfew, illuminance limits) are locally defined and vary widely — don't assume model-ordinance language was adopted verbatim by a given jurisdiction
Residential-adjacent parcels often carry stricter limits than commercial-zoned parcels within the same ordinance
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?