Low voltage path lights answer one planning question: can people follow the route? A commercial crossing raises a different one: can people in and near the crossing be seen? That second question needs its own assessment. It is not an automatic order for more fixtures.
In this guide, the "second layer" means that separate coverage decision, not extra path lights or a specific product. The clearest supported example is a roadway crosswalk. For pedestrian-only crossings and open transitions, you record site conditions and send them to project review. We don't treat any path-light model as a proven fit for crossing coverage here.
Route Guidance and Crossing Coverage Are Separate Planning Questions
Route guidance stops answering the crossing question once people have to be seen across a wider space, not just guided along a line. Path lights mark edges and direction. A crossing asks whether a person stands out to the people who need to see them, such as drivers approaching a crosswalk.
For roadway crosswalks, the Federal Highway Administration lists specific crosswalk visibility conditions that can reduce visibility. These are poor lighting, obstructions such as parked cars, and horizontal or vertical roadway curvature. FHWA says crosswalk lighting should light pedestrians with positive contrast so drivers can identify them more easily. Put simply, the person should look brighter than what's behind them from the driver's view. FHWA also calls for luminaires placed in forward locations so the pedestrian isn't seen as a silhouette.
That is why a row of low voltage path lights leading up to a crosswalk doesn't settle the crosswalk question on its own. The fixtures may guide the walk well and still not be placed to light a person from the driver's side. If a commercial walkway meets a roadway crosswalk with any of those conditions, flag the crosswalk for a separate visibility assessment.
The assessment might find that existing light is adequate. It might also find that a fixture should move, or that a different lighting layer is needed. In every case, it is a decision step, not a fixture count. FHWA's crosswalk guidance does not set a matching trigger for pedestrian-only crossings or open transitions, so those settings get a different next step below.
Use Site Conditions to Decide What Needs a Separate Assessment
The setting decides which next step applies. Roadway crosswalks and intersections have federal guidance behind them. Pedestrian-only crossings and open transitions get a documented record, not a pass/fail test.
| Setting and observations | What it supports | Next step |
|---|---|---|
| Roadway crosswalk with poor lighting, obstructions, or roadway curvature | FHWA visibility concern | Flag for separate visibility assessment |
| Roadway intersection: nighttime crash history, traffic and non-motorized user volumes, crosswalks or raised medians, transit stops and boarding volumes | FHWA roadway-intersection lighting factors agencies consider | Add to the review record as context |
| Pedestrian-only crossing or open transition | Site record only; no tested threshold | Mark unresolved; send to project review |
The two roadway rows rest on FHWA guidance for roadways. They are not a checklist for every private walkway. The intersection factors are things agencies weigh when deciding about lighting, not mandatory criteria. Use them to describe the site, not to reach a verdict.
At any crossing, build the same site record. Note the crossing footprint and the view from each approach. Mark where the route edges end and whether the path opens into a wider plaza, lot, or drive aisle. Record existing nighttime light from building fixtures, poles, or signs, and note whether it actually reaches the crossing. List anything that blocks sight lines, such as parked vehicles, planters, or signage. Finally, sketch the paths people really take, including shortcuts that skip the marked route.
The approach-to-destination mapping in our guide to service entrance transitions works the same way here. Document the geometry first, then think about fixtures. If the crossing sits inside a parking lot, note which existing area lights reach it. Our breakdown of parking lot distribution patterns explains how Type III and Type V optics spread light, which helps you describe that existing coverage accurately.
For a pedestrian-only row, the outcome stays "unresolved pending review." That label is useful. It keeps a roadway trigger from being reused where nothing supports it.
Turn a Possible Gap into a Project-Specific Review Brief
When the site record points to a possible gap, write a short brief that asks a visibility question, not a fixture question. Then check documentation for the exact model you're considering before you choose anything.
- Name the setting. State whether this is a roadway crosswalk, a pedestrian-only crossing, or an open transition. Describe who moves through it and in which directions.
- Attach the site record. Include the matching table row, approach views, route edges, existing light, obstructions, and observed movement paths.
- State the open question. Ask something like "Are people visible across the crossing and on both approaches after dark?" Don't ask for a generic fixture count.
- Identify the authority when jurisdiction matters. Rules vary by location, so confirm who reviews lighting for your site. As one local example, Seattle's street lighting guidance says pedestrian ways not next to a roadway may require lighting as determined by the Traffic Engineer. That applies to Seattle public-street projects, not to private sites or other cities.
- Route actual design to a qualified professional. FHWA's pedestrian lighting primer says a qualified lighting designer should perform the actual design steps and finalize the plans. Circuit design, wire sizing, and code compliance also sit outside this brief. Those belong to a licensed electrician and the authority having jurisdiction.
- Match exact-model documents to the brief. Review the current spec sheet and photometric files for the specific model or variant. Our guide to reading photometric data covers IES files and uniformity metrics. Whether you're comparing landscape lighting options, LED post top lights, or LED area lights, judge each model by its documents, not its category name or product title.
The brief gives the reviewer a defined crossing objective and real site conditions. That's what lets them answer the coverage question instead of guessing.
FAQs
Does FHWA crosswalk guidance cover a private walkway that never meets a drive aisle?
No. The FHWA conditions discussed here are written for roadway crosswalks and roadway intersections. For a walkway that stays pedestrian-only, record the site conditions and treat the coverage question as open until a project reviewer weighs in.
Can this guide tell me path light spacing or how many fixtures a crossing needs?
No. Spacing and quantities depend on project design and on the photometric data for the exact model you install. The guide helps you frame the question so a designer can answer it.
Are low voltage path lights ever enough at a crossing?
They can be part of the answer. A review may find that existing light plus route fixtures covers the crossing. That conclusion comes from the project assessment, not from the fixture category.
If one city has a rule for pedestrian ways, does it apply to my site?
Not automatically. A local rule like Seattle's applies within that city's public-street projects. For your site, identify the local authority and the requirements that govern your project.
