Build real technology
Design sensors, PCBs, 3D-printed hardware, calibration rigs, embedded systems, camera rigs, and experimental tools that can actually be deployed.
Project Nightfield is a student-led network combining engineering, AI, data science, field research, astronomy, and conservation to understand nighttime environments, build tools that make them measurable, and turn evidence into real local improvement.
Nightfield is for high school and college students who want something more hands-on than another awareness club. You can join as a builder, coder, researcher, data person, field scientist, designer, or organizer and own a real piece of the system.
Design sensors, PCBs, 3D-printed hardware, calibration rigs, embedded systems, camera rigs, and experimental tools that can actually be deployed.
Work on web infrastructure, data pipelines, GIS, Nightfield Atlas, visualization, firmware, automation, or open-source research tools.
Explore machine learning, computer vision, deep learning, TinyML, site-prioritization models, and rigorous evaluation on real environmental problems.
Calibration, uncertainty, sensor drift, geospatial data, satellite observations, field measurements, validation, and before-versus-after analysis all matter here.
If you prefer fieldwork, run approved Night Audits, study actual sites, meet community stakeholders, and help move a recommendation toward implementation.
Nightfield is still in its founding pilot. Early contributors can help define the hardware, research methods, software, datasets, and culture rather than inheriting a finished system.
A CAD student, Python programmer, electronics builder, machine-learning researcher, statistics person, astronomy student, environmental scientist, outgoing organizer, or someone who simply likes experimenting can all contribute to the same mission.
Nightfield connects scientific evidence to action. Whether the evidence comes from a field observation, a student-built sensor, a GIS pipeline, or an ML model, the loop stays the same.
Collect structured observations, sensor readings, images, environmental context, or remote data using a documented method.
Turn the strongest evidence into a realistic recommendation for the responsible school, campus, park, municipality, or organization.
Return after a change, repeat a comparable measurement, and distinguish real improvement from assumption.
Neither path is secondary. Nightfield needs people who can collect credible evidence and people who can invent the tools, software, models, and infrastructure behind that evidence.
Study schools, parks, campuses, observatories, nature areas, and community spaces. Record conditions, identify something actionable, work with the responsible organization, and return for follow-up evidence.
Build sensors, mechanical systems, electronics, calibration tools, GIS infrastructure, data pipelines, AI, deep-learning models, and open technology that makes environmental fieldwork more scalable.
Use them to understand Nightfield's current method, priority project ideas, data-quality expectations, and safety boundaries. Then improve them through real pilot experience.
Nightfield Labs is the engineering and computational core of the network. We're looking for students who like building prototypes, breaking assumptions, calibrating sensors, writing code, working with imperfect data, training models, and turning experiments into usable tools.
This is a helpful project template, not a rulebook. It contains the current build ideas we're actively interested in, possible MVPs, testing expectations, AI/ML directions, hardware pathways, and ways different teams can connect. Read it first so you can improve an existing direction instead of accidentally duplicating work.
Build a low-cost, open nighttime environmental sensing node for repeatable light, temperature, humidity, and optional privacy-conscious acoustic measurements.
Test inter-device variation, linearity, repeatability, temperature drift, enclosure effects, and correction models so cheap sensors can produce more comparable data.
Build an interactive map combining Nightfield sites, audits, interventions, NightNode data, and properly attributed remote nighttime-light context.
Develop a computer-vision screening system for standardized, permission-cleared fixture imagery, with site-level testing, uncertainty, and human review built into the workflow.
Use environmental, geospatial, and remote features to help identify where limited field time could generate the most useful new evidence.
Build a safe low-voltage experimental lighting rig with interchangeable 3D-printed shields and quantitatively compare how geometry redirects light.
Explore DSP and TinyML using local spectral features and broad environmental sound categories without making raw conversation storage the default.
Once a prototype is actually validated, translate it into a reproducible PCB with documented sensors, connectors, test points, power, and hardware revisions.
Design a repeatable phone or camera mount, angle procedure, and metadata workflow that reduces uncontrolled variation in computer-vision datasets.
A project counts when it improves measurement quality, reduces field effort, helps choose better sites, supports an intervention, improves data reliability, or makes an environmental result easier to verify. "Used AI" by itself is not the goal.
The Night Audit is designed to be approachable enough for a new team while still producing structured evidence that can connect to Nightfield Labs.
Use this guide before your first audit. It is intentionally a starter template: keep the core method consistent, then improve the workflow after real pilot feedback. It also explains how field teams can contribute data to Atlas, NightNode, NightVision, and future ML work.
Use an established citizen-science observing method instead of inventing an arbitrary Nightfield darkness score.
Document targeting, spill, glare, controls, operation, and other potentially correctable conditions.
Record habitat, land use, astronomy context, local constraints, and relevant environmental observations.
Document broad nighttime sound sources and connect future quantitative work to validated or calibrated setups.
A mechanical student, embedded developer, ML researcher, GIS contributor, field team, and outreach lead can all touch the same project before it becomes a verified result.
This is the long-term Nightfield pipeline we're trying to build.
Nightfield's dashboard is a working template during the founding pilot. The point is to eventually report what actually happened: audits, validated builds, interventions, follow-ups, and verified improvements.
The spreadsheet is a starting template. Metrics should populate only as reviewed work is completed.
Nightfield is deliberately avoiding a giant hierarchy of decorative titles. The founding team should stay small, technical where appropriate, and accountable for actually shipping work.
Coordinates direction, execution, technical development, field science, and partnerships.
Maintains audit methodology, data-quality expectations, and follow-up standards.
Coordinates NightNode, CAD, electronics, calibration, and engineering projects.
Coordinates NightVision, site-prioritization, model evaluation, and responsible ML practice.
Builds GIS, data pipelines, analytics, database structure, and Nightfield Atlas.
Maintains the site, repositories, forms, automation, and digital systems.
Finds strong contributors and helps them become active teams instead of passive members.
Builds legitimate relationships with educators, astronomy groups, researchers, and conservation organizations.
Turns completed experiments, builds, audits, and interventions into clear public stories.
Field teams can use the official Globe at Night workflow for citizen-science sky observations instead of Nightfield inventing its own unsupported scale.
Nightfield field screening can reference the Five Principles for Responsible Outdoor Lighting: Useful, Targeted, Low Level, Controlled, and Warm-Colored.
Nightfield Labs may use appropriately licensed and attributed Earth-observation and mapping resources for remote environmental context.
Project Nightfield Network is currently an independent, student-led, noncommercial initiative.
Minimal collection. Nightfield should collect only information reasonably needed to coordinate participants, review contributions, operate teams, and measure project impact.
Participants should not submit home addresses, government identification, financial information, passwords, private schedules, or other unnecessary sensitive information.
Public impact reporting should use aggregate, site-level, or non-identifying information whenever practical. Private participant contact information should not appear on the public impact dashboard.
Nightfield does not sell participant personal information.
Questions concerning information controlled directly by Nightfield may be sent to nightfieldnetwork@gmail.com .
Participants under 18 should follow applicable parent or guardian, school, club, property, and site requirements.
Do not publicly post another participant's private phone number, home address, private email, schedule, or unnecessary identifying information.
Identifiable photographs, videos, or quotations involving minors should not be publicly published by Nightfield without appropriate permission.
Night Audits are observational activities and should occur only in safely accessible, permitted locations.
Do not trespass, enter restricted areas, stand in roadways, climb lighting structures, open installed electrical equipment, interfere with wildlife, or physically modify public lighting.
Nightfield Labs student hardware projects should remain within appropriate low-voltage electronics, mechanical prototyping, software, data science, and supervised research activities.
Installed mains-powered lighting should be handled only by appropriately responsible or qualified personnel.
Nightfield AI systems are experimental research and screening tools.
NightVision and related models should not be represented as professional engineering inspectors, regulatory tools, or replacements for human review.
Model evaluation should use appropriately separated data where relevant and should document limitations, uncertainty, and failure cases.
A flashy training-set accuracy number is not evidence that a model works in new communities, new cameras, or new environments.
References to external organizations, programs, datasets, methods, or frameworks do not imply sponsorship, funding, certification, endorsement, or formal partnership.
Third-party names, logos, trademarks, datasets, photographs, publications, and other materials remain subject to the rights and licenses of their respective owners.
Nightfield should not use another organization's logo as Nightfield branding or claim a partnership until that relationship actually exists.
NASA Earth-science datasets used in Nightfield work should be cited at the dataset/product level where appropriate.
If OpenStreetMap data is used in Nightfield Atlas, the required contributor attribution and applicable Open Database License notice must be displayed.
The Five Principles for Responsible Outdoor Lighting should remain properly attributed to DarkSky International and the Illuminating Engineering Society.
Student observations, experimental models, and prototype sensors may contain measurement uncertainty, device variability, observer variation, environmental effects, calibration error, or other limitations.
Nightfield observations are not professional electrical inspections, engineering certifications, regulatory determinations, or guarantees of site safety.
Published work should distinguish between raw measurement, analysis, prediction, recommendation, implemented action, and verified result.
Project Nightfield Network is currently an independent, student-led, noncommercial initiative. Participation and leadership roles are currently unpaid.
Participation does not guarantee employment, financial compensation, academic credit, college-admission benefit, research authorship, or leadership status.
Responsibility should follow real contribution, reliability, judgment, and continued involvement.
Pick a site. Design a sensor. Build a map. Train a model. Run an experiment. Analyze a dataset. Talk to a community. Fix a broken method. Start with one useful contribution.