Car park lighting map
Car park lighting mixes vehicle movement, pedestrian movement, exposure and spill-light concerns. A basement bay, open-air bay, apartment driveway, retail parking row, loading edge, ramp, stair landing and pedestrian path can each need a different lighting record. The estimate should name whether the main question is beam spread, a simple zone allowance, exterior exposure or a standards boundary.
The beam angle calculator is the main route when pole, wall, eave or canopy mounting controls where the light lands. The room lighting calculator can support a simple covered zone estimate when the car park area is being treated as one defined floor zone. The Australian lighting level planning table gives planning context before a value is carried into the calculation. The outdoor floodlight planning guide keeps spill-light, aiming and exposure notes visible.
Search intent split by parking record
Car park searches often begin with a broad place name, but the useful record starts with the movement path, mounting condition and boundary. Keep vehicle, pedestrian, ramp, exposure and road-interface questions apart before a value is compared.
| Search phrasing | Stronger lighting record | Why it should stay separate |
|---|---|---|
| Car park lighting | Bay row, movement path, mounting height, target plane and control state. | A full-site average can hide ramps, entries, paths and exposed edges. |
| Basement car park lighting | Covered floor zone, columns, low ceiling, obstruction shadows, UF and MF. | Basement records use different exposure and maintenance assumptions from open bays. |
| Outdoor parking lighting | Pole or wall beam footprint, site-edge direction, IP note and spill direction. | Open-air records need aiming and exposure notes before ordinary floor results are trusted. |
| Car park ramp lighting | Sloped route, driver eye direction, transition contrast and glare line. | Ramp visibility and driver glare are not the same as bay-floor light. |
| Pedestrian path in car park | Continuous route, step or crossing edge, dark gaps and after-hours state. | Pedestrian records should not be buried inside vehicle bay estimates. |
| Car park sensor lighting | Active mode, timeout, dimming level, measured condition and connected load. | A reading only makes sense when the same control state is recorded. |
| Road edge or public footpath interface | Site boundary, authority context, spill direction and project record. | Public-space context is outside a simple car park estimate. |
Parking zone schedule
A car park estimate becomes safer when the record names the movement path and boundary before any value is compared. A bay row, basement aisle, ramp, pedestrian crossing and road edge may sit on one drawing while needing different geometry, exposure and review notes.
| Parking condition | Assessed surface | Better route | Boundary to keep visible |
|---|---|---|---|
| Open bay row | Bay floor, pole line and site-edge direction. | Beam angle calculator plus outdoor spill and glare. | Spill beyond the target area and neighbour-facing glare are separate from bay visibility. |
| Covered or basement bay | Floor zone, columns, ceiling height and obstruction shadows. | Room lighting calculator plus maintenance factor. | A covered-zone estimate should not be reused for open-air exposure. |
| Ramp or driveway | Sloped route, driver eye direction and entry transition. | Beam angle coverage plus lux meter reading records. | Driver glare and transition contrast need notes beyond an average floor result. |
| Pedestrian path or crossing | Continuous route, step edges and dark gaps. | Downlight spacing calculator plus task-plane records. | Pedestrian records should not be hidden inside the vehicle bay estimate. |
| Lift lobby or building entry | Threshold, wall faces and transition from car park to interior. | Apartment common area page plus lighting control records. | Interior common-area lighting and car park lighting need separate records. |
| Road interface | Boundary with a public road, footpath or authority-controlled area. | Road lighting categories table. | Public-road context is not approved by a car park estimate. |
Route the car park question
| Parking question | Primary page | Keep beside the record |
|---|---|---|
| Beam spread from a pole or wall fitting | Beam angle calculator | Mounting height, target plane, beam angle and aiming direction. |
| Covered parking bay estimate | Room lighting calculator | Zone area, target plane, luminaire output, UF and MF. |
| Pedestrian path beside parking | Downlight spacing calculator | Effective height, beam overlap and dark gaps. |
| Exposure or water/dust note | IP ratings table | Complete luminaire rating, mounting orientation and location. |
| Spill-light or neighbour concern | Outdoor lighting spill and glare table | Intended surface, boundary direction and project documents. |
| Public road or authority context | Road lighting categories table | Category context, road interface and source boundary. |
| Measured-light record | Lux meter reading records | Readings tied to bay, ramp, path, entry or crossing condition. |
| Operating state | Lighting control records table | Full-output, sensor, dimmed, after-hours and curfew states kept separate. |
Assessed planes and zone splits
Car park calculations should start from the surface and movement path being assessed. Vehicle bays, ramps, pedestrian paths and building entries create different records even when they share a site plan. Keep open-air and covered zones separate so exposure, spill and transition notes do not get folded into one floor-area estimate.
| Assessed surface | Record as | Calculator or table link |
|---|---|---|
| Parking bay floor | Defined floor zone with mounting and obstruction notes. | Room lighting calculator |
| Pole or wall beam footprint | Beam spread at the target plane. | Beam angle calculator |
| Pedestrian path or crossing | Continuous route with overlap and dark-gap note. | Downlight spacing calculator |
| Ramp or driveway | Sloped movement path with driver glare note. | Outdoor spill and glare table |
| Road interface | Public-space context kept outside the early estimate. | Road lighting categories table |
Parking zones
Parking areas are often over-simplified because the floor area is easy to measure. The harder problem is deciding which surfaces matter. A driver needs bay and ramp visibility. A pedestrian needs path, step and face-level orientation. A neighbouring property or road edge may need light controlled away from the target zone.
Open car parks need weather and spill-light notes. Basement or covered car parks need transition and shadow notes. In both cases, the estimate should avoid pretending that one wattage or lumen figure settles visibility, glare, exposure and public-space context.
| Zone | Calculation focus | Secondary check |
|---|---|---|
| Open bay row | Beam spread and overlap across the bay area. | Spill beyond site edge and pole sightlines. |
| Basement parking | Defined floor zone and obstruction shadows. | Low ceiling, columns and transition at entries. |
| Ramp or driveway | Surface visibility along the slope. | Glare into drivers and adjacent windows. |
| Pedestrian path | Continuous route and step contrast. | Dark gaps, wayfinding and vertical brightness. |
| Loading edge | Task plane and vehicle approach. | Workplace record and obstruction from vehicles. |
Mounting, exposure and control notes
Mounting height, aiming direction and obstructions usually drive the car park record. A pole, wall bracket, soffit fitting and low basement luminaire can all produce a different distribution on the same measured area. Record the mounting condition before comparing outputs.
| Condition | Lighting note to keep | Why it matters |
|---|---|---|
| Pole-mounted open bay | Mounting height, aiming direction and site-edge spill. | Beam spread and boundary direction can dominate the result. |
| Low basement ceiling | Fitting spacing, columns and vehicle shadowing. | Averages can hide dark areas behind obstructions. |
| Ramp or driveway | Driver eye direction and adjacent window line. | Glare can matter before the floor estimate looks low. |
| Coastal or exposed site | IP rating, corrosion exposure and cleaning condition. | Enclosure language belongs beside the mounting note. |
| Timed, sensor or dimmed operation | Occupancy mode and after-hours state. | Control settings change the practical lighting condition. |
| High connected load | Input watts, zone area and operating hours. | Load density is separate from visibility, glare and road context. |
For open areas, read outdoor floodlight planning with beam angle coverage. For covered or basement areas, keep maintenance factor and utilisation factor with the room or workplace calculation record. Where the question is energy or load, keep lighting power density examples beside the calculation without treating watts per square metre as a visibility result.
Basement, open-air and road-edge separation
Basement and open-air parking should not share one record. Basement areas often need obstruction, low-ceiling, transition and maintenance notes. Open-air areas often need aiming, exposure, spill direction and site-edge notes. A ramp can need both because it changes height, sightline and surrounding brightness as the user moves.
| Separation trigger | Keep as a separate record | Why it matters |
|---|---|---|
| Roof or canopy changes | Basement bay, covered bay, open bay and entry canopy. | Exposure, maintenance and distribution assumptions change. |
| User path changes | Vehicle bay, ramp, pedestrian path, stairs and lift entry. | Driver and pedestrian visibility are not the same task. |
| Boundary changes | Neighbour window, site edge, public road and building entry. | Spill, glare and authority context need their own notes. |
| Control state changes | Full-output, sensor, dimmed, after-hours and curfew state. | A measured result can only be compared with the same active condition. |
| Obstruction changes | Columns, parked vehicles, landscaping, signage and ceiling services. | Average values can hide dark gaps and shadowed surfaces. |
Exposure and standards boundaries
The IP ratings table should be read when fittings sit outdoors, near wind-driven rain, dust, insects or cleaning water. The IP code belongs to the complete luminaire and does not choose cable entries, mounting methods or maintenance access. The luminaire markings table keeps IP, lumens, watts, CCT, CRI/Ra and driver notes from being collapsed into one fitting description.
The Australian lighting standards table and road lighting categories table keep public-space context visible. This page does not turn parking, road or public-area lighting into a pass/fail calculator. It routes early estimates to the right geometry, exposure and standards-boundary pages.
Where a car park touches a public road, public footpath, neighbouring property, school entry, clinic entry or apartment lobby, keep a separate line for that interface. The public estimate can record the car park zone, but public-road lighting, neighbour spill, accessible paths, emergency lighting and building-entry criteria belong in the relevant project documents and boundary pages.
Car park record path
For a first record, draw the zone, name the user path, name the mounting condition, then choose the page that owns the arithmetic. Keep beam angle, mounting height, target surface, luminaire output, input watts, IP note and spill-light direction together. If the car park interfaces with a public road, neighbouring property or formal project brief, the public estimate should remain a planning note beside project-specific review.
| Record item | Car park-specific detail |
|---|---|
| Zone name | Open bay row, basement bay, ramp, driveway, pedestrian path, stair landing or loading edge. |
| Assessed plane | Floor surface, sloped path, pedestrian route, wall sign, entry threshold or road interface. |
| Geometry | Area, mounting height, beam angle, aiming direction, column layout and obstruction note. |
| Calculation inputs | Luminaire output, UF, MF, watts, spacing and target table reference. |
| Quality notes | Spill direction, glare line, IP rating, control mode, measurement condition and maintenance access. |
| Review boundary | Road, public-area and project-specific documents kept separate from the early estimate. |
Supporting car park checks
Car park records should also describe transitions. A driver moving from a bright street to a covered bay, or a pedestrian moving from a lift lobby to an open path, may notice contrast more than the average value. Columns, parked vehicles, ramps, landscaping and signs can all block light after the first estimate is made. When those conditions are present, keep a short obstruction note beside the calculation.
Energy and control notes also belong with the record. Operating hours, dimming schedules, sensors and after-hours access can change the value of a lighting estimate without changing the geometry. Keep lighting control records and lighting power density examples separate from standards-boundary notes so the page stays useful for early planning without pretending to approve a public lighting design.
When a car park connects to an apartment lobby, school entry, clinic entry or workplace loading area, keep the adjacent sector record separate. The bay estimate, path estimate, entry transition and public-road context may all point to different calculators or tables.
For terminology, keep spill light and glare beside the outdoor table when a fitting can be seen from an approach path, neighbouring window or road edge.