Parking-lot lighting layouts and checks · hosted tool

Parking-lot lighting layouts you can re-check in AGi32.

New lot: draw where poles may go, and it searches for the fewest new poles that meet your targets, telling you whether every layout with fewer poles was tried. Existing lot: keep the poles, and it tries every candidate fixture and aiming you allow, so nobody has to try them one by one, or it tells you none works. Every input is on record.

or watch the research engine search (research, not the hosted tool)
reading the siteResearch engine run on a synthetic 300 × 200 ft lot
473 of 473 points within 0.13 % of AGi32research run of our engine on a real parking-lot project: given poles, horizontal illuminance · reported, not independently reviewed
Within 0.5 % on 271 pointsresearch engine: parking lot, min, average and max vs an AGi32 direct-light run
Within 3.6 % of AGi32 and DIALuxresearch engine, 2023 roadway study: area averages, 9 zones
25 of 25 acceptance tests passresearch engine, real parking project, last run 2026-10-08
first deployment · California lighting company, related to Runnax
research engine · replay of a recorded run · on-request runs paused

Watch the research engine search

Research — Runnax Engine study. This is the research engine searching regular pole arrays. The hosted tool has its own layout search inside the areas you allow, for new lots or added poles. What was compared with AGi32, and where it ran.

Runnax runs a hosted parking-lot lighting tool: on existing poles it picks the luminaire and aiming among the candidates you choose; for a new lot it searches for the fewest new poles inside the areas you allow, and says whether every layout with fewer poles was tried. Runnax Engine, shown below, is our research engine; its runs are published as research, with every input on record so you can check them in AGi32.

Compared with AGi32 on a real parking-lot project (research run; reported, not independently reviewed) · research engine labelled as such · every input on record

Watch it lay out a 300 × 200 ft lot. Poles may only go on the islands and curbs (teal).

0layouts tried
0rejected
1poles
searching…
0 / 0
run of 2026-10-14·
—
—poles
—heads · — ft
—avg fc
—min fc · max:min —

What it does today

Live

Parking lots

  • New lots: draw where poles may and may not go; it searches for the fewest new poles (1 to 6) that meet your horizontal targets, rechecks the top three with a full calculation and says whether every layout with fewer poles was tried
  • Existing lots: keep the poles; it computes every candidate luminaire (2 to 4 per run) within the aiming ranges you allow and keeps the lowest declared input power among those that pass, or says none does; or keep the poles and add the fewest new ones, with the same statement. Models can be assigned per pole position, for example existing and new poles
  • Targets per area or for all areas together; your own IES files, each checked before you can enable it; a site plan image (PNG/JPEG) you trace by hand
  • Research engine (not in the hosted tool): searches regular arrays up to 16 poles and 3 rows and keeps the layout with the fewest poles it found that pass; not a proven minimum
Calculation

Roadways

  • Research engine, 2023 roadway study: single-side arrangement validated against AGi32 and DIALux on real projects
  • Opposite and median arrangements calculate; check their numbers in AGi32 or DIALux for now
  • Roadway and sidewalk grids, each with its own statistics; BUG rating from the IES file
  • Area averages are validated; point values and minimums are not yet, so no roadway pass/fail
Live

Checks you set

  • Property-line light against the limits you enter, at sample points (direct light)
  • GR glare at up to 8 observer points you choose: a reported value, not a pass/fail
  • B-U-G rating and zonal lumens of each luminaire, disclosed; vertical targets on given poles
  • An optional RP-8-25 reference reading next to your own targets

None of these is a compliance determination; the engineer of record still signs the design.

How it works

Upload & mark

Upload a site plan image (PNG or JPEG; what image works), set the scale and check it with three lines of known length (one sets the scale, one horizontal and one vertical check it), draw the areas to light, then either place the existing poles with their mounting heights or draw where new poles may and may not go. Setbacks and height limits are asked once, with their source, and go into the report.

Requirement & candidates

Enter the average or minimum illuminance (fc or lx) and the uniformity per area, upload or pick the luminaire IES files you consider, and set the aiming range you allow for each head. Add property-line limits, GR observer points or vertical targets (given poles) if you need them.

Calculate & download

Point-by-point illuminance on every area. On given poles the tool tries the candidate luminaires and aimings and returns the combination that meets the requirement, or says none does within the allowed range; for a new lot it returns the layout with the fewest new poles it found, says whether every layout with fewer poles was tried, and you confirm each pole base before the final run. You get a result page, a customer report (HTML and PDF) and a ZIP package your engineer can check in AGi32: installation table with tilt, fixture list, point-by-point, per-area and property-line CSVs, BUG and GR tables and the layout basis, in English or Chinese.

Calculation time depends on the number of candidates and the aiming range; at busy times jobs queue.

Move the poles yourself

Research — Runnax Engine study. This is the research engine searching regular pole arrays. The hosted tool has its own layout search inside the areas you allow, for new lots or added poles. What was compared with AGi32, and where it ran.

Same lot, same luminaire table the engine used, same point method, running in your browser. Drag a pole along the islands, change the height, watch the grid. This is a preview; the engine's run above is the record.

drag a pole along the islands · double-click to add · right-click to remove
—
—avg fc
—min fc
—max : min
—poles

Luminaire: the one the engine picked for this lot, measured IES. Grid 10 ft, direct light only, same point method as the engine.

What one research-engine run looks like

Research — Runnax Engine study. This is the research engine searching regular pole arrays. The hosted tool has its own layout search inside the areas you allow, for new lots or added poles. What was compared with AGi32, and where it ran.
24,904layouts tried for this lot
18,721thrown out for a pole off the islands
64 ssearch, start to finish
1kept: the fewest poles found that pass (not a proven minimum)
hover a point: engine vs AGi32

Engine grid, 271 points at 20 ft, 15 heads. Against an AGi32 direct-light run of the same lot, min, average and max agree within 0.5 %.

Real project (research engine): a municipal sports-complex parking lot, South Dakota

Customer asked
Eavg ≥ 1.0 fc · Avg:Min ≤ 3.3
Fixture
75 W · 13,000 lm · 25 ft
Delivered design (AGi32)
1.2159 fc · 3.1998 · PASS
Engine, same lot
1.2367 fc · 3.1312 · PASS

The engine reads 1.7 % higher on average than the delivered design; the tighter of the two leaves 3.04 % headroom on uniformity. Direct light only; not an RP-8 compliance statement; headroom is specific to this lot.

Open the case →

Already have an AGi32 layout?

The AGi32 file check is paused. We are not accepting files: no upload, and please do not email files. Meanwhile, you can run your own IES on given poles in the hosted tool, with a free sign-up (about the AGi32 file check, a sample result).

  1. AGi32 file check pausedNo files are accepted, by upload or by email.
  2. Meanwhile, in the hosted toolSign up free, place the poles from your layout, use the same IES files and compare the horizontal illuminance yourself.
  3. Questions about a layoutYou can still ask us about a parking-lot lighting question by email; we answer as soon as we can and promise no turnaround.

Sign up free

Why not a manufacturer's free layout?

Research — Runnax Engine study. This is the research engine searching regular pole arrays. The hosted tool has its own layout search inside the areas you allow, for new lots or added poles. What was compared with AGi32, and where it ran.
Manufacturer free-layout serviceRunnax
TurnaroundPublished turnaround for free manufacturer and distributor layouts: typically 1–3 business daysFree sign-up; upload your IES and site image and run it yourself, no waiting for someone to draw it. Calculation time depends on the candidates and aiming range; at peak times jobs queue.
Whose fixturesThat manufacturer's catalog onlyYour own IES files
Same 300 × 200 ft lot (research engine)Archipelago's free online tool, 2026-10-16: 12 × 150 W, average 3.1 fc against the 2.2 fc asked (41 % over); the tool marks its results unvalidatedResearch engine: 8 × 166 W, poles only on the islands, 0.2 fc minimum met

Turnaround as published by Archipelago Lighting (team layout, 3 business days), Jarvis Lighting (2–3 business days) and LED Lighting Supply (2–3 days outdoor); LED Light Expert (1–3 business days) and Commercial LED Lights (24–48 h) from search snippets; all checked 2026-10-16. Lot row: Archipelago's tool asks for an average target and the research engine searched on a minimum, so it compares capability, not scores.

How to get it

Free trial

Self-service
  • Sign up with your work email
  • 30 calculations per organization, up to 5 per day
  • Results are for evaluation only
  • No credit card
Free

Start free trial

Partner deployment

Lighting companies
  • Deployed for one partner by arrangement (Auvolar, a related company)
  • Ask us if you want it for yours
By arrangement

Ask a question

Talk to an engineer

Questions about a lot or the tool
  • Leave a question in the contact form
  • Or write to kyan@runnax.com
We reply as soon as we can

Ask a question

What you need to know

What do you need from me?

For the hosted tool: a site plan image (PNG or JPEG) with three lines of known length (one sets the scale, one horizontal and one vertical check it), the IES file of each luminaire you consider, the existing pole positions and heights or the areas where new poles may go, and the illuminance your customer requires. No files by email.

How close is it to AGi32?

On a real parking-lot project with given poles, 473 of 473 grid points agree with AGi32 within 0.13 % (horizontal illuminance; a research run of our engine on a real parking-lot project, not yet repeated in the hosted tool; the first run failed until the 1 m arm offset was entered; reported, not independently reviewed). Research engine: on a real lot, its minimum, average and maximum are within 0.5 % of an AGi32 direct-light run of the same lot over 271 points; against the AGi32 design delivered to that customer, its average reads 1.7 % higher. Roadway (2023 research study): area averages are within 3.6 % of AGi32 and DIALux on 9 zones from real projects. Roadway point values and minimums differ more, so we don't quote them on their own.

Does it certify RP-8 compliance?

No. It calculates with the RP-8 point method and checks the targets you enter, for example values you take from RP-8 for your lot. Property-line light, GR glare and BUG are reported against the limits you enter, never as compliance. A run is direct light only, not a compliance statement and not a construction approval; the engineer of record still signs the design.

Where can it put poles?

In the hosted tool, inside the areas you allow, for a new lot or for extra poles on an existing lot: it searches for the fewest new poles (1 to 6, one model and one height) that meet your horizontal targets and says whether every layout with fewer poles was tried. Existing poles are never moved; arms, foundations and ground conditions are not modelled. The replay on this page is a different search: Runnax Engine research on regular arrays of up to 16 poles in up to 3 rows.

What can't it do yet?

It does not read CAD, PDF or AGi32 files or recognise stalls, aisles or poles from an image (you draw them); it does not build a site from dimensions alone; it does not move existing poles; there is no chat assistant; reflections, obstructions, terrain and roadway criteria are not modelled, and vertical targets are for given poles only. Results are simulations, not field measurements and not compliance determinations.

Do you train on my files?

Your projects (site images, plans, luminaire files and results) are not used to improve Runnax Engine or to publish benchmarks. AI features are currently off and no data is sent to AI services.

Who is behind Runnax?

Runnax was founded by Wally Hei (Founder & CEO), who has more than 20 years in lighting manufacturing and export and leads Auvolar, a California lighting company. Kyan Gao (Head of Product & Engineering) builds the engine and the product. Auvolar is the first company to use Runnax, so it is a related customer.

Ask about your lot or the hosted tool

Questions about a layout, the tool, or a white-label deployment: leave your work email and a sentence; we reply as soon as we can. Please do not send files here — upload them inside the tool. Research-engine runs on request are paused. How we use data

Or talk to an engineer

If you'd rather describe the project first, or you're evaluating the tool or a white-label deployment, write to the founder directly.

kyan@runnax.com

Book 15 minutes

US Pacific. We answer as soon as we can; no turnaround is promised.