IES Photometric Files for Roadway Lighting (Type II/III/IV)

Request model-specific IES / LDT photometric files for roadway lighting simulations, tender review, and consultant checking. Sunlurio matches files by product family, optics, wattage, mounting condition, and document purpose.

Engineering boundary: IES / LDT files are controlled references. Project-specific files are released after model and project review, not as random public downloads.

IES / LDT File Request Path

Start with the checklist and request a matched file path after basic project review. Public previews show the document structure only; actual IES / LDT files depend on confirmed model, optics, wattage, mounting condition, and document purpose.

IES and LDT photometric files for solar street light project review

Input checklist before file matching

IES LDT and DIALux lighting design file review for street lighting engineering stage

Project-matched IES / LDT delivery preview

Sunlurio photometric test report for street lighting project review

Photometric report / polar evidence preview

Request Project-Matched IES / LDT Support

Inputs needed: product family, model direction, optics or beam angle, wattage, mounting height, arm condition, road or application type, DIALux / Relux use case, and BOQ or tender requirement where applicable. We use these inputs to avoid photometric mismatch and trace the selected file back to the proposed luminaire.

Controlled release depends on complete model, optics, mounting, and project-purpose inputs.

Sunlurio photometric test report for street lighting project review

How IES / LDT Files Are Matched

The review path links road geometry, mounting condition, optical distribution, wattage, and document purpose before a matched file path is released for DIALux / Relux or tender review.

1. Confirm Product Family and Model Direction

Confirm product family, model direction, road or application type, and the project purpose before file matching.

2. Match Optics / Wattage / Mounting Condition

Match beam angle or roadway distribution, wattage, mounting height, arm condition, and installation geometry.

3. Confirm File Purpose

Confirm whether the file is for tender review, DIALux / Relux simulation, consultant review, BOQ checking, or internal selection.

4. Release Matched IES / LDT Path After Review

Release the matched file path after review. If layout, spacing, mounting, wattage, or optics change, the file should be checked again.

Related Resources

Use these related paths when the IES file must connect to a BOQ, datasheet, DIALux report, drawing package, or tender submission. Related paths: DIALux / Relux Support, Drawings & Datasheets, Tender / BOQ Support, Submit Project RFQ, and Resource Center.

Engineering White Papers

Reference notes for optics, maintenance factor, poles, batteries, and tender review.

Tender / BOQ Support

Match IES file requirements with BOQ lines, model codes, and tender clarification notes.

Datasheets & Drawings

Connect photometry to model datasheets, mounting drawings, poles, and approval references.

Installation Manuals

Use wiring, installation, commissioning, and handover references after the file path is confirmed.

FAQ: IES Files for Roadway Lighting Projects

At minimum, we need road width, pole height, and pole spacing. If available, share arm length, road class, target uniformity, CCT/CRI, dimming profile, and a Google Map link or layout—this helps us match faster and avoid rework in simulation.
Yes. We select the distribution based on your road geometry and mounting conditions, then return the matched IES set with a polar plot preview and matching notes for tender and simulation use.
Yes. Our IES files are prepared for standard roadway lighting simulation workflows. To keep results defensible, we also provide orientation and mounting-range notes with the delivery pack.
Typical response time depends on project completeness, layout availability, and file matching requirements. If inputs are missing, we confirm them first to avoid mismatch.
Roadway lighting performance depends on distribution selection + mounting height + spacing + road width. Using an unmatched IES file often leads to poor uniformity, glare, or spacing rework, which can delay approvals and site acceptance.

Request a Project Document Pack

Share your project location, road width, pole height, spacing, working hours, backup days, and required documents. Our team can help prepare configuration guidance, datasheets, IES/LDT files, DIALux support when applicable, drawings, and BOQ matching notes.