A street-light photometric design converts verified road geometry, target criteria, pole data, and a model-specific photometric file into calculation results that can be reviewed before procurement. The workflow should test alternatives, document assumptions, and carry the approved fixture, optic, output, mounting, and control settings into installation and field verification. This guide is for lighting designers, engineers, contractors, consultants, and technical procurement teams deciding whether a roadway layout is ready to approve.
The central decision is not simply whether a software report shows an acceptable average. It is whether the complete model, input files, operating states, and review criteria represent the installation that will actually be purchased and built.
Establish the design basis
Begin by defining the exact roadway segment and the criteria that will determine acceptance. A calculation cannot compensate for an unclear project brief. Before opening DIALux or another lighting program, record the road cross-section, traffic or use conditions, surface assumptions, calculation grids, pole constraints, operating states, and maintenance assumptions.
A design-basis register should separate mandatory project criteria from working assumptions. Mandatory criteria may come from the project owner, a road authority, a contract, or a locally adopted standard. Recognized references such as ANSI/IES RP-8-22 and CIE road-lighting publications can inform the method, but they do not automatically establish the acceptance criteria for every country or roadway. Confirm the applicable edition, metric, authority, and calculation method before modeling.
| Register item | What to record | Why it changes the result |
| Roadway scope | Segment limits, lanes, medians, shoulders, sidewalks, crossings, and transitions | Determines which surfaces and boundaries are calculated |
| Performance basis | Illuminance or luminance criteria, uniformity, glare, and other required metrics | Defines what “pass” means; average illuminance alone may be insufficient |
| Calculation grid | Grid points, evaluation zones, spacing, and boundary treatment | Changes minimum values and how dark bands are detected |
| Pole constraints | Existing or proposed coordinates, height, setback, outreach, arm, and tilt limits | Limits the feasible layout alternatives |
| Operating states | Full output, scheduled dimming, sensor states, and failure or fallback states where required | Each state may produce a different result |
| Maintenance assumptions | Light-loss or maintenance factor, surface condition, and inspection basis | Converts initial photometry into a maintained design assumption |
Do not mix criteria and assumptions in one undifferentiated note. For example, a required maintained uniformity value is not equivalent to an assumed maintenance factor. If an input is unknown, mark it as pending rather than letting the software default become an invisible project decision.
The first practical output should be a signed or reviewable design basis, not a screenshot of a preliminary layout. It gives the calculation team a stable reference and makes later changes traceable. If the project is actually a parking facility rather than a roadway, use the related parking garage lighting design and buying guide to establish the different application inputs.
Validate the source files and luminaire configuration
The photometric file must represent the luminaire configuration that may be ordered. A visually similar fixture or a file downloaded from an earlier revision is not sufficient. Match the product family, exact model, wattage or output setting, optic, tilt convention, and file revision before placing the luminaire in the roadway model.
IES files are a standardized electronic way to transfer photometric data and related information; the Illuminating Engineering Society provides both an explanation of IES files and the relevant file-format method. The format itself does not prove that a file is current, tested for the intended configuration, or correctly oriented in the software. Treat file control as a technical document-control task.
File-control checklist
- Confirm the file name, product model, output setting, optic, CCT or configuration identifier, and revision date.
- Confirm whether the file uses tested absolute photometry or relative photometry that depends on a separate lamp or luminaire output assumption.
- Check the source laboratory or manufacturer document and preserve the original file without editing its photometric values.
- Confirm the intended mounting orientation, roadway-side direction, tilt reference, and rotation convention.
- Verify that the software imports the file without a warning, missing data, unexpected luminous flux, or incorrect dimensions.
- Compare the file summary with the formal luminaire schedule used for procurement.
- Record any dimming state, control setting, or output percentage used in the calculation.
Absolute and relative data should not be treated as interchangeable. If the file represents a normalized distribution, the calculation team must know what output assumption scales it. If the project uses a selectable-output luminaire, the selected output must appear in the model, schedule, submittal, and approval record.
DIALux’s official street-lighting guidance describes a workflow based on a street profile, an appropriate standard, and documented calculations. That supports using the software for repeatable design analysis, but software output remains dependent on the validity of the project inputs and product data.
Build the roadway and pole geometry
Translate the approved drawings into a reproducible calculation model. Start with the road surfaces and lane arrangement, then add sidewalks or adjacent areas only when they are inside the project scope or acceptance criteria. Define pole coordinates from a controlled drawing or survey rather than estimating positions from a rendered image.
At minimum, record the pole setback, mounting height, outreach, arm type, luminaire position, and tilt. For a two-sided or staggered arrangement, preserve the actual relationship between opposing or alternating poles. A small change in setback or arm length can change the lateral distribution, uniformity, and boundary results even when the nominal wattage remains unchanged.
Model-input screenshot list
Capture enough evidence that another reviewer can reproduce the model without guessing:
- Project settings showing units, calculation method, maintenance assumptions, and selected criteria.
- Plan view showing road edges, lanes, pole coordinates, spacing, setbacks, and orientation arrows.
- Cross-section or 3D view showing mounting height, arm projection, luminaire tilt, and relevant elevations.
- Calculation-grid settings for each roadway or sidewalk surface.
- Luminaire properties showing the exact file, output, optic, rotation, and tilt.
- Operating-state or dimming settings for each scenario.
- Any simplified obstruction, boundary, surface, or transition assumption.
Document simplifications explicitly. A straight road model may be reasonable for a uniform segment, but it should not silently represent a curve, intersection, crest, driveway, pedestrian crossing, or nearby building that changes the lighting requirement. Likewise, a clear-road model should not be presented as proof for an installation with trees, overhead structures, barriers, or large signs unless those conditions are outside the design scope.
The model should be identifiable by a revision number and linked to the source drawing. This is what makes a roadway simulation auditable instead of merely presentable.
Run and compare design alternatives
Use the calculation to solve the project, not to validate one preselected fixture. Create controlled scenarios that change one meaningful design variable at a time where practical. Useful variables include optic, output, pole spacing, single-side versus staggered layout, arm projection, mounting height, tilt, and dimming state.
Keep the comparison criteria, surface assumptions, grid, and maintenance factors consistent. Otherwise, an apparent improvement may result from changing the evaluation method rather than improving the lighting design. A scenario name should state the configuration clearly, for example: “Option B — 150 W, Type IV optic, staggered layout, scheduled output state.”
| Alternative | Controlled change | Keep constant | Review question |
| A: baseline | Existing spacing and selected optic | Road model, grid, criteria, maintenance factor | Does the starting configuration meet the defined basis? |
| B: optic change | Narrower or wider distribution | Output, height, spacing, orientation | Does the distribution improve coverage without creating boundary problems? |
| C: spacing change | Pole spacing or layout pattern | Luminaire file, output, height, grid | Is uniformity improved at an acceptable installation quantity? |
| D: mounting change | Height, arm, setback, or tilt | Road geometry and evaluation criteria | Does geometry solve the issue more effectively than more output? |
| E: control state | Dimming or scheduled output | Physical geometry and photometric file | Does each operating state remain within its applicable criterion? |
Compare alternatives using the metrics that matter to the project: maintained average or target value, minimum value, uniformity, glare metrics where required, spill or boundary results, energy or control implications, procurement availability, and installation constraints. Do not select the highest average simply because it is the largest number. Excess output can worsen glare, trespass, or energy use while leaving an uneven layout unresolved.
A good alternatives matrix also records the reason for rejection. “Failed minimum at the outer grid” is more useful than “not preferred.” It preserves design knowledge for the next revision and prevents the team from repeating a weak option after a supplier or drawing change.
Review results beyond the average
An acceptable average does not demonstrate an acceptable roadway design. Review the minimum values, uniformity, glare metrics where required, calculation boundaries, transitions, and contours. The result review should answer where the design is weak, under which operating state, and whether the weakness is caused by the fixture, the geometry, or the evaluation setup.
Inspect calculation grids and contour maps for dark bands between poles, localized peaks below the luminaire, abrupt changes at the segment ends, and unusual bright or dark strips at boundaries. A smooth-looking false-color image is not a substitute for the numeric result table. Check that the contour scale does not hide the difference between a pass and a marginal result.
Structured result-review checklist
- Confirm that the reported average, minimum, maximum, and uniformity values use the intended grid and surface.
- Review the minimum point location, not only the minimum number.
- Check the longitudinal and transverse pattern between adjacent poles.
- Inspect the first and last calculation intervals, transitions, intersections, driveways, and pedestrian areas in scope.
- Review glare or threshold-increment metrics when the selected method requires them.
- Check boundaries for unintended spill, abrupt cut-off, or a falsely favorable calculation area.
- Run and review every scheduled output or dimming state separately.
- Confirm that the maintenance factor and surface assumptions are visible in the report.
- Compare the approved scenario with the luminaire schedule and installation drawing.
- Record reviewer comments, disposition, and any required recalculation.
The choice between an illuminance-based and luminance-based method can change the inputs and interpretation. Surface properties, observer position, traffic context, and the selected project method may matter when luminance is used. Do not convert one method into the other by replacing a target number without changing the underlying model and criteria.
DIALux street-lighting calculations, like any roadway lighting simulation, are only as reliable as the source file, road geometry, criteria, and assumptions. The software can document a result; it cannot independently confirm that the chosen road class, local requirement, mounting condition, or procurement configuration is correct.
Issue an approval package and preserve the design intent
The approval package should connect the calculation to procurement, installation, commissioning, and future maintenance. It should allow a reviewer to identify exactly what was modeled and what must be preserved when the luminaire is ordered and installed.
Include the following approval deliverables:
- Design-basis register with project criteria, assumptions, maintenance factor, and exclusions.
- Source roadway drawings or controlled geometry references.
- Software name and version, calculation method, project file revision, and report date.
- Photometric file name, revision, model, output, optic, orientation, and source record.
- Luminaire schedule with quantity, mounting arrangement, voltage or control state, and installation interface.
- Plan and cross-section views showing pole coordinates, spacing, height, setback, arm, and tilt.
- Result tables and contours for every required operating state.
- Alternatives matrix and the reason the approved option was selected.
- Notes on assumptions, exclusions, boundaries, transitions, and field verification.
- Submittal and commissioning checks that tie the installed product back to the approved design.
Define changes that require recalculation before installation or acceptance. These include a different luminaire model, wattage, output setting, optic, photometric-file revision, mounting height, arm, setback, tilt, pole spacing, pole location, road geometry, surface basis, or control state. A substitution that appears electrically similar may still have a different distribution and therefore requires a new photometric review.
For a project-specific calculation, provide FY LIGHTING with the road drawing, pole schedule, mounting dimensions, target maintained criteria, voltage, control states, and project destination. FY LIGHTING can supply the relevant SLE photometric data and support a configuration review for the project team’s formal design process. The exact model, output, optic, file revision, installation geometry, and destination requirements should be confirmed before the design is issued.
Field verification closes the workflow. Confirm the installed model and orientation, record any changed pole or arm dimensions, verify the control schedule, and perform the agreed inspection or measurement. If the installation differs from the approved model in a way that can change the result, preserve the change record and recalculate rather than treating the original report as automatically transferable.
Conclusion: Make the photometric model traceable
Street light photometric design is a controlled decision workflow, not a single software screenshot. Establish the roadway criteria, validate the exact photometric file, build geometry from controlled drawings, compare alternatives under consistent assumptions, review minimums and boundaries, and preserve the approved configuration through procurement and commissioning.
The practical next step is to assemble the road drawing, pole schedule, mounting dimensions, maintained criteria, voltage, control states, and project destination. For a broader product-selection workflow, review the commercial LED street-light resource before matching the exact file and configuration. Send those inputs to FY LIGHTING for a configuration review based on the exact roadway application, then keep the approved file and installation geometry linked to the final submittal.
Frequently Asked Questions
Is DIALux enough to approve a street-light design?
No. DIALux can calculate and document a roadway model, but approval also depends on valid road geometry, applicable criteria, correct maintenance assumptions, and a photometric file that represents the product configuration being procured. The reviewer should check minimums, uniformity, boundaries, glare metrics where required, and each operating state before approving the design.
What files are needed for a roadway calculation?
At minimum, prepare a controlled road drawing, pole schedule or coordinates, cross-section and mounting dimensions, applicable performance criteria, surface assumptions, calculation-grid requirements, operating or dimming states, and the exact luminaire photometric file. Include voltage, control information, transitions, sidewalks or adjacent areas in scope, and any known obstructions that can affect the model.
Should dimmed conditions be calculated separately?
Yes, when dimming changes the output or operating condition used for acceptance. A layout that passes at full output may not meet its maintained criterion at a scheduled lower output, and a control state can also affect the documented energy or commissioning requirement. Model each required state with its actual output setting and review the applicable results separately.
When must a design be recalculated?
Recalculate when a change can alter the photometric distribution, mounting geometry, evaluation area, or operating state. Typical triggers include a different model, optic, output, photometric-file revision, mounting height, arm, setback, tilt, pole spacing, pole location, road geometry, surface assumption, or dimming state. Preserve the revision trail so procurement and installation do not drift from the approved design.
Sources
- DIALux: Street Lighting with DIALux evo— official software guidance on street profiles, standards, and documented calculations.
- Illuminating Engineering Society: RP-8-22, Recommended Practice: Lighting Roadway and Parking Facilities— official standard listing for roadway and parking-facility lighting practice.
- CIE: Road Lighting Calculations, 2nd Edition— official publication page for road-lighting calculation methods.
- CIE: Lighting of Roads for Motor and Pedestrian Traffic, 2nd Edition— official publication page for road-lighting recommendations.
- IES: Learn About IES Files— official explanation of IES photometric files.
- FY LIGHTING: LED Street Light— product-family reference for project-specific street-light photometric data.
- FY LIGHTING: Parking Garage Lights— related application guide when the project is a parking facility rather than a roadway.
