Roadway Lighting Design Guide

What You Actually Need to Know Before Opening Any Software

The Roadway Lighting Design Guide is a set of standards and procedures used by civil engineers and lighting designers to plan, calculate, and document the illumination of roads, highways, and parking facilities. It isn't one single document you download from the internet. It's a collection of references, mostly from IESNA, AASHTO, and local municipal codes, that together dictate how bright a road needs to be, what kind of luminaire to mount, where to place poles, and how to prove it with calculations. When someone says "I need a Roadway Lighting Design Guide," they usually mean the process of applying those references to a specific project. I spend most of my time doing this work for municipal clients, and the part that trips up junior engineers every single time isn't the photometric calculation itself. It's understanding that different road classes demand fundamentally different maintenance factors and mounting heights, and if you treat them the same, the design fails inspection on day one. I once designed a residential street using the same maintenance factor as a highway. The municipality rejected it because the projected light output after ten years of lamp depreciation and lens dirt accumulation didn't meet minimum average illuminance. It took me three weeks to redo the calculations with the correct MF values from IES RP-8. That was a costly mistake that taught me to double-check the class designation before running any software.

Roadway Lighting Design Guide: Where to Get the References

There is no single PDF that covers everything. The primary sources are the IES Lighting Handbook, IES RP-8 Roadway Lighting, and the AASHTO Green Book for geometric design parameters. Some states also publish their own supplementary standards, like Caltrans or NYSDOT, which override or supplement the national guidance. You should also check with the local authority having jurisdiction early, because a small town might have requirements that are stricter than IES RP-8 in ways that aren't obvious from reading the standard alone. The IES RP-8 standard is the backbone. It defines the road classes from R1 through R5, plus special areas like tunnel entrances and pedestrian zones. Each class has prescribed minimum average illuminance, uniformity ratios, and glare control requirements. For example, an R-3 road typically requires around 10 foot-candles average illuminance with a uniformity ratio of at least 4:1, while an R-5 might only need 2 foot-candles. The numbers shift when you're dealing with LED luminaires versus traditional HID fixtures because LED systems often achieve better uniformity at lower power levels, but the standards still reference the old baseline categories. For software, the most widely used tool is AGA LightTools or DIALux. DIALux is free and handles roadway calculations adequately for most projects. AGA is more expensive but produces reports that municipalities accept more readily because the calculation engine is IES-certified. I use DIALux for initial layout and concept work, then switch to AGA for the final submission documents. The difference in output quality between the two programs is noticeable when you're comparing uniformity maps on complex intersections.

The Calculation Process

Start by determining the road class from the traffic volume and function. This is usually defined by the transportation engineering team on the project, not the lighting designer, so get that document before you start calculating. Next, select a luminaire family from the manufacturer catalogs. Don't just pick the first LED fixture that looks good. Look at the IES photometric file, check the beam spread, and verify that the candela distribution matches the mounting height and spacing you're planning to use. A Type III distribution at 30 feet behaves very differently from a Type V at the same height, and getting this wrong means either over-lighting the road or leaving dark spots near the poles. Set the mounting height, arm length, and spacing interval. These three variables are interdependent. If you increase the mounting height, you can increase spacing, but you lose some uniformity. If you shorten the arm length, you reduce cut-off glare but might create uneven patches on the roadway surface. I typically iterate through four or five combinations before settling on one, and I run the calculation after each change. A single run in DIALux takes about two minutes on a modern laptop. Doing this by hand would take hours and still wouldn't account for the real-world luminous intensity distribution of the fixture. The critical output values are average illuminance, minimum illuminance, and the uniformity ratio, which is the average divided by the minimum. Most municipal inspectors check the uniformity ratio first because it's the easiest metric to verify visually. A uniformity ratio worse than 4:1 is almost always a red flag. Glare rating is another metric, usually expressed as the Threshold Increment percentage. Keep TI below 20 percent for most roadway applications. Anything above that causes discomfort glare, and drivers will complain even if the illuminance numbers look fine on paper.

Common Mistakes That Waste Time

The biggest mistake I see is not accounting for lumen depreciation properly. LED drivers degrade, optics yellow, and lenses collect road grime. The maintenance factor in your calculation should reflect the actual projected light output after three to five years, not the initial rated lumen output from the manufacturer. I've seen designs that met illuminance targets on paper but fell short within two years because the designer used the initial lumen value instead of the LLDF, or Luminaire Light Depreciation Factor, combined with the LDDF, or Lamp Light Depreciation Factor. Multiply those two numbers together and apply them to your initial lumen output, and you get the realistic design value. Another frequent error is ignoring pole placement at intersections. A single pole at a corner doesn't illuminate the crosswalk or the turning lane adequately. You need at least two poles on a standard four-way intersection, positioned to cover both approaches. I learned this the hard way on a project in suburban Virginia where the city rejected my initial design because the turning radius zone had a uniformity ratio of 7:1, far worse than the required 4:1. I added two additional poles and recalculated, which brought the ratio down to 3.2:1 and passed inspection on the second submission. Tunnel lighting is a completely different beast. The threshold zone, transition zone, and interior zone each have separate illuminance requirements that change based on the external daylight level and the tunnel length. I worked on a mountain tunnel project where the threshold zone required over 5,000 nits of luminance because the entrance was exposed to direct sunlight at a sharp angle. The standard roadway calculations don't apply here. You need a dedicated photometric simulation with sky condition modeling, and the cost per fixture is significantly higher because you're using high-output optical systems with precise shielding.

When the Standard Doesn't Cover Your Situation

Not every project fits neatly into an R-class designation. Shared-use paths, industrial access roads, parking lot aisles, and emergency vehicle routes all have unique requirements. For a shared path next to a roadway, you might need to coordinate with the pedestrian lighting standards in IES RP-20, which emphasizes uniformity and low glare over raw illuminance. For an industrial site, OSHA and NFPA 70 may impose additional requirements around hazardous locations that affect fixture selection and mounting height. If you're designing for a facility with forklift traffic, you need to consider vertical illuminance, not just horizontal, because operators need to see at eye level. Sometimes the local code goes beyond what IES RP-8 specifies. I've encountered jurisdictions that require dark-sky-compliant fixtures on all new roadway installations, even on highways, which limits the available luminaire options significantly. In those cases, you may need to use upward-light-restricted fixtures with lower total lumen output and compensate with closer pole spacing. This increases the number of poles and the initial cost, but it's the only way to comply. I've also seen projects where the municipality required specific color temperature ranges, like 3000K maximum for residential areas, which eliminates many high-efficiency LED options that only come in 4000K or 5000K. There are situations where the standard guides simply don't work well together. For instance, a highway project that passes through a historic district might have conflicting requirements between AASHTO sight distance standards and local historic preservation guidelines about pole appearance and placement. I dealt with this on a state route project in North Carolina where the DOT wanted standard 40-foot poles at 200-foot intervals, but the historic commission required decorative poles hidden in landscaped buffers at 120-foot intervals. The solution was to use a higher-output luminaire on the decorative poles and reduce the spacing to meet both the illuminance targets and the aesthetic requirements. It cost more, but it avoided another round of review submissions.

Documentation and Submission

Your final submission should include a lighting layout plan, an IES report with illuminance values at all critical points, a pole schedule with make and model, and a maintenance factor calculation showing how you arrived at the design lumens. Some municipalities also require a glare analysis report and a photo of the proposed fixtures installed on similar poles for visual review. I usually prepare six to eight pages of documentation for a standard roadway project, and the process from initial layout to final submission takes about four to six hours for a straightforward design. A complex intersection or tunnel project can take two to three days. If you're looking for a starting point, the IES webpage at ies.org/resources/technote.html has the RP-8 technical note available for purchase, and DIALux offers free training modules on roadway calculations. Many luminaire manufacturers also publish design guides that include sample layouts and calculation spreadsheets tailored to their product lines. These are useful for quick estimates but shouldn't replace a full photometric analysis for permit submission. The key takeaway is that roadway lighting design is more about understanding the interaction between the standard, the fixture, and the site conditions than it is about running software. The software gives you numbers, but the numbers only mean something if you understand what they represent. A uniformity ratio of 3:1 might look good on a screen, but if the poles are placed along a curved section without adjusting the aim, the actual driving experience could feel uneven and unsafe. Walk the site if you can, or at least pull satellite imagery and study the geometry before you finalize the pole locations. That habit alone has saved me from more redesigns than I can count.