Grow Light Fixture Dataset

What the Grow Light Fixture Dataset contains

The Grow Light Fixture Dataset is the machine-readable version of PlantLightIndex's fixture catalog and measurement layer. It combines product identity and specifications with explicit measurement status so users can distinguish a fixture that has a usable PPFD curve from one that only has wattage, PPF or marketing specifications.

The current public distribution covers 14 fixture records and the stored manufacturer PPFD observations connected to them. It is generated from the same records used by the fixture database and distance tools.

Measured values, estimates and recommendations are different things

PlantLightIndex treats a measurement as an observation, not automatically as a recommendation. A PPFD reading taken at a leaf tells you how much photosynthetically active photon flux reached that position at that moment. A published greenhouse treatment tells you what researchers supplied under a particular experiment. A photosynthetic light-saturation point describes a physiological response. A practical indoor reference is an editorial recommendation intended to help a houseplant grower make a decision. Those records can inform one another, but they are not interchangeable.

This distinction prevents a common failure in plant-light advice. A plant may survive under a very low PPFD treatment while growing slowly or changing form. Another study may show photosynthesis continuing to increase until a much higher PPFD. Neither number, by itself, proves that the lower value is ideal or that the higher value should be used in a home. PlantLightIndex therefore stores measurement context, evidence scope, source type and recommendation status alongside the number.

Missing evidence stays visible

Some plant profiles contain a practical numerical PPFD range. Others show only a parent-species or genus reference. Some remain qualitative because a defensible species- or cultivar-specific numerical target has not been established in the sources reviewed for the site. That unevenness is intentional. A database becomes less useful when every empty field is filled with a plausible-looking number.

When a value is absent, the site should explain what is known instead. A page may state that a plant is commonly described by an extension source as preferring bright indirect light, or that a cultivar has demonstrated a different physiological response from its green parent, without converting those statements into a precise household target. The calculators then change behavior according to the record: full, contextual or qualitative.

Product identity and specification fields

Fixture ID and slug identify the PlantLightIndex record. Brand, product name and model preserve manufacturer naming. Fixture type distinguishes bulb, bar, panel, pendant, track and other forms. Electrical power, spectrum, color temperature, CRI, PPF, beam angle, dimming, timer, coverage, base and lifespan are included when the manufacturer source supports them.

Null does not mean the fixture lacks a feature in the real world. It means PlantLightIndex has not stored a verified value for that field in the current source record.

Why PPF and PPFD are separate

PPF describes the total photosynthetic photon flux emitted by a fixture, measured in µmol/s. PPFD describes how densely those photons arrive at a surface, measured in µmol/m²/s. A fixture can have a published PPF while its PPFD-distance curve remains unknown.

For that reason, PPF never enables the distance finder by itself. The CSV exposes both fields so analysts can compare fixture output without confusing total emission with canopy intensity.

Measurement count and measurement series

The dataset includes the number of stored PPFD points and a serialized measurement series containing distance, PPFD, dimmer setting and source ID. Those points are the evidence used by distance matching. A two-point series can support bounded interpolation but may receive lower confidence than a denser series.

Measurement points from incompatible dimmer settings or product revisions should not be treated as one continuous curve. PlantLightIndex keeps source IDs attached to each series so discrepancies can be traced.

Data status

Multi point indicates several compatible PPFD-distance observations. Single point means a numerical reading exists but no curve can be defined. Spec only means product specifications are available without usable numerical PPFD-distance data. Conflicted is reserved for records where current evidence should not be merged automatically.

These categories are more actionable than a generic “data available” flag because they determine what the calculators are allowed to do.

Distance-finder eligibility

The distance-finder field is a reviewed boolean. It is enabled only when the fixture has enough compatible points for bounded interpolation. Even then, the algorithm cannot extrapolate beyond the stored measurement span. A user should measure the actual canopy because room geometry, fixture orientation and plant size can still change the delivered PPFD.

A false value does not rate the fixture negatively. It rates the completeness of the measurement record.

Measurement confidence

High, Medium and Limited confidence describe the quality of the stored fixture evidence. Confidence can reflect the number and spacing of points, consistency of the source and whether the exact current product page supports the values. Sparse endpoints can support a useful estimate while remaining explicitly less certain.

Commercial manufacturer data are treated as primary product evidence but remain labeled as manufacturer measurements. Independent or PlantLightIndex measurements can be added later as separate source classes rather than overwriting the original.

Product URLs and source IDs

The product URL points to the manufacturer page used for identity/specification context when available. Source IDs connect the row to the public Source Library. Measurement-source IDs identify the records that specifically support PPFD points.

The canonical dataset page uses those source URLs as provenance in Dataset structured data. Google recommends isBasedOn when an aggregated dataset derives from multiple originals. See Google Search Central and Schema.org DataDownload.

How to interpret a fixture row

Multi-point, distance-enabled

The fixture can participate in plant matching when the plant has a numerical reference and the target overlaps the stored PPFD span. The returned distance is still an interpolation unless it lands exactly on a stored point.

Single-point or spec-only

The fixture can be compared by specifications, but a downstream application should not invent a distance curve. Wattage, PPF and beam angle can explain the fixture, not replace measured PPFD.

Conflicted

Treat the record as requiring revision-specific review before automated matching.

How the CSV stays aligned with the website

The endpoint serializes the current fixture and measurement arrays at request/build runtime. The same fixture IDs, source IDs and measurement points power the website. Validation checks source references, duplicate slugs, measurement ownership and distance-finder requirements.

This architecture means the public data distribution grows with the product rather than being maintained as a disconnected spreadsheet.

Recommended uses

• Audit which fixtures have usable PPFD-distance evidence.
• Compare PPF and power without treating either as leaf-level PPFD.
• Build manufacturer/source coverage reports.
• Join fixture curves to plant practical ranges for private analysis.
• Identify products where independent testing would add the most value.
• Track conflicts and product revisions without discarding old provenance.

For the rules that govern the matching engine, read the Grow-Light Measurement Methodology.

Why a spec-only fixture still belongs in the dataset

Users often need to know that a fixture exists and what the manufacturer publishes even when PlantLightIndex cannot calculate a distance. Excluding all spec-only products would make the database look more complete than the market evidence really is. Keeping them visible exposes the measurement gap.

The distance-finder eligibility field then prevents those incomplete records from entering numerical matching. Discovery and calculation are separated rather than forcing one threshold for both.

How fixture rows support research prioritization

Sorting by data status and popularity can show which products would benefit most from independent measurement. A widely used spec-only fixture is a better testing candidate than an obscure model already supported by a dense manufacturer map. Conflicted records can be prioritized for revision verification.

This turns missing data into a roadmap rather than a reason to invent values.

Fixture dataset QA checklist

• Fixture IDs and slugs are unique.
• Every stored measurement references a valid fixture and source.
• Distance-enabled fixtures have enough compatible points.
• Spec-only fixtures do not contain fabricated PPFD curves.
• Measurement series preserve distance and dimmer context.
• Manufacturer product URLs match the intended model.
• Conflicting revisions remain separate or clearly flagged.
• Affiliate URLs do not affect evidence fields or matching eligibility.

The result is a dataset that describes both what is known and what remains unmeasured.

Change management for fixture data

Fixture data require special care because products can change without a completely new marketing name. When specifications shift, editors should determine whether the change is a corrected page, a regional version or a genuine hardware revision. Measurements from different revisions should not be combined until compatibility is established.

Stable fixture IDs are useful only while they refer to a consistent product identity. A materially different revision can justify a new fixture record with its own slug and measurement series. Older records can remain available when they still correspond to products users own, provided the page explains the revision context.

Affiliate and other commercial URLs should remain separate from evidence source IDs. That separation prevents monetization changes from rewriting dataset provenance and keeps the measurement layer independent from referral relationships.

Using the fixture CSV for comparison without turning it into a ranking

A spreadsheet can group fixtures by brand, form factor, power, PPF, data status or measurement confidence. Those comparisons are descriptive. They should not be converted directly into a “best” score because the dataset does not measure every factor that matters to a buyer, such as build quality, price, warranty, thermal behavior or uniformity across every canopy size.

For measurement analysis, first filter to fixtures with multi-point data and distance-finder eligibility. Then inspect the serialized measurement series and source IDs. A fixture with points from 12 and 48 inches provides a very different evidence shape from a fixture with three closer points. Confidence should stay visible when comparing interpolated ranges.

PPF can be useful for understanding total photon output across fixture classes, but it should remain separate from the PPFD series. A high-output panel may spread photons over a wide area while a smaller bulb creates a concentrated center point. Plant matching is based on the PPFD curve because the plant experiences photon density at its leaves.

When the same product family has regional or revision differences, do not combine rows manually without checking the source pages. The dataset is designed to preserve product identity and provenance so those differences can be investigated rather than averaged away.

If you build a private fixture-ranking model, keep measurement completeness as a separate dimension from product desirability. A product with sparse data should not automatically rank poorly as hardware; it should rank as less certain for PPFD-distance analysis.

Coverage also deserves its own field or analysis when reliable maps exist. One center PPFD value can be excellent for a small plant and misleading for a wide canopy. Until standardized coverage measurements are available, the fixture dataset deliberately avoids turning a center reading into an assumed average across an area.

A future expanded distribution could separate measurement points into a second normalized CSV with one row per fixture, distance, dimmer setting and sensor position. The current compact series is easier for ordinary spreadsheet users, while the underlying TypeScript arrays already retain point-level structure. Any future format should preserve the same source identifiers and compatibility rules.