AGi32 exterior lighting workflow: Importing CAD and placing poles
A step-by-step AGi32 workflow for exterior lighting. Clean complex CAD backgrounds, define calculation grids, and optimize pole placement for parking lot designs
Mastering the workflow in AGi32 for exterior lighting design is essential for producing accurate photometric calculations that comply with local ordinances and industry standards. The transition from a raw architectural or civil CAD file to a fully calculated 3D photometric model requires precision at every step. Engineers and lighting designers rely on AGi32’s robust calculation engine to ensure that light levels, uniformities, and spill light restrictions are rigorously met across complex sites. Without a structured methodology, importing CAD data can lead to calculation errors, software crashes, and inaccurate illuminance grids that fail to reflect the true physical environment.
The core of a successful AGi32 exterior project lies in data preparation and systematic execution. Extraneous lines, unresolved blocks, and unpredictable Z-axis elevations within DWG or DXF files frequently disrupt the 3D meshing process. By establishing a strict pre-import cleaning routine, designers can eliminate these variables before they enter the lighting calculation environment. Once a clean geometric foundation is established, the placement of luminaires and calculation grids must follow a logical sequence to accurately simulate how light behaves across parking lots, walkways, and property boundaries.
This technical guide outlines an optimized, step-by-step workflow for executing exterior lighting designs in AGi32. From the initial scrubbing of complex CAD backgrounds to the strategic definition of calculation grids and pole placement, this approach minimizes processing overhead and maximizes photometric accuracy. The methods detailed herein are designed to handle demanding commercial and municipal projects, ensuring that lighting power densities, uniformities, and property line trespass limits comply with standards such as those established by the Illuminating Engineering Society (IES).
Core Concept Definitions
Before initiating the AGi32 workflow, it is necessary to define the fundamental concepts that govern the software’s calculation environment. Understanding these elements ensures that the structural integrity of the photometric model is maintained throughout the design process.
DWG and DXF Formats: These are the standard vector file formats utilized for importing 2D and 3D geometric data into AGi32. DWG is the native binary file format for AutoCAD, while DXF (Drawing Exchange Format) is a cross-platform ASCII standard. Ensuring compatibility and proper scaling during the import of these files is the critical first step in defining the site boundaries and physical obstructions.
3D Meshing Engine: AGi32 relies on a radiosity-based calculation engine that discretizes geometric surfaces into a fine 3D mesh. The accuracy of inter-reflected light calculations is directly proportional to the quality of this mesh. If the imported CAD background contains overlapping lines, unclosed polygons, or extreme Z-axis anomalies, the meshing engine may produce calculation artifacts or fail entirely during the radiosity process.
Calculation Grids: These are mathematically defined planes within the 3D environment where point-by-point illuminance values are computed. For exterior lighting, calculation grids are typically placed at grade (Z=0) for horizontal illuminance, but may also include vertical planes at property lines to assess light trespass. The density of the calculation points within the grid directly impacts the statistical accuracy of minimum, maximum, and average illuminance metrics.
Luminous Intensity Distribution: This defines how a specific luminaire distributes light into the surrounding space, typically derived from IES LM-63 photometric data files. In AGi32, the luminaire definition must accurately pair this distribution data with the correct light loss factors, electrical load, and physical housing geometry to accurately simulate real-world performance.
Pre-Import CAD Preparation Strategies
The most common source of error in AGi32 exterior lighting projects stems from poorly prepared CAD backgrounds. Civil and architectural files often contain vast amounts of extraneous data that are irrelevant to photometric calculations but impose severe computational penalties. A rigorous CAD cleaning protocol is mandatory prior to import.
Flattening the Z-Axis
Civil engineering drawings frequently contain topographic contours, utilities, and landscaping elements scattered across varying Z-axis elevations. If imported directly into AGi32, these disparate elevations can cause the software to interpret the site as a complex 3D terrain, which may not be the intent for a standard flat-plane parking lot calculation. The result is unpredictable grid placements and distorted luminaire mounting heights.
To resolve this, all linework intended to represent the flat grade plane must be collapsed to an elevation of zero. In AutoCAD, commands such as FLATTEN or manipulating the properties to set all Z-coordinates to 0.00 are standard procedures. This ensures that when the calculation grid is placed at Z=0, it perfectly aligns with the visual representation of the site boundaries and parking stalls.
Purging and Exploding Blocks
Nested blocks—blocks within blocks—are notoriously problematic for AGi32’s import engine. These complex structures often contain hidden layers or data that fail to translate accurately, resulting in missing geometry or application instability. Furthermore, dynamic blocks with multiple visibility states may import incorrectly.
The best practice is to isolate the critical linework—curbs, property lines, building footprints, and existing utility poles—and explode nested blocks down to simple polylines and lines. Following this, running the PURGE command removes unused layers, linetypes, and block definitions from the file. This process significantly reduces the file size, ensuring a swift and stable import into AGi32.
Layer Management and Isolation
CAD files typically include layers for water lines, sewer systems, and obscure text annotations that clutter the visual environment and provide no value to the lighting calculation. Importing these layers into AGi32 increases the memory footprint and complicates the selection of relevant geometry.
Prior to import, turn off or freeze all non-essential layers. Create a streamlined version of the drawing using a WBLOCK (Write Block) command, capturing only the geometry necessary for defining the illuminated areas and physical obstructions. Key layers to retain include property boundaries, hardscape outlines, building perimeters, and relevant landscape features that might block light.
The AGi32 Import and Setup Process
Once the CAD file has been rigorously prepared, the import process within AGi32 sets the foundation for the calculation environment. Attention to scale and origin positioning is critical at this stage to ensure spatial accuracy.
Importing the DWG/DXF File
Navigate to the AGi32 import menu and select the prepared CAD file. During the import dialog, the software will attempt to determine the units used in the original drawing. It is essential to verify this setting. If the civil drawing was drafted in decimal feet, ensuring AGi32 interprets the units as feet rather than inches is paramount. An error here will scale the entire site incorrectly, rendering all photometric calculations invalid by a factor of 12.
Furthermore, ensure that the import settings are configured to bring in 2D lines and polylines as background geometry rather than 3D objects, unless specifically importing 3D building models for shadow analysis. Background geometry does not interact with the radiosity engine, significantly reducing calculation times while still providing the visual references needed for layout.
Establishing the Coordinate Origin
Civil drawings often use state plane coordinate systems, placing the site geometry millions of units away from the 0,0,0 origin point. While AGi32 can handle large coordinates, working excessively far from the origin can occasionally introduce graphical artifacts or floating-point precision errors during complex calculations.
It is recommended to utilize AGi32’s translate function during or immediately after import to move the primary site geometry closer to the global origin. Selecting a prominent corner of the property line or the main building footprint and shifting it to 0,0,0 simplifies camera navigation and ensures maximum computational stability.
Defining the Calculation Environment
With the site geometry established, the next phase involves defining the areas where illuminance will be calculated and analyzed. This requires the strategic placement of calculation grids and the definition of statistical zones.
Creating Horizontal Calculation Grids
Horizontal calculation grids are the primary tool for verifying compliance with IES guidelines for parking lots and walkways. In AGi32, grids can be defined using simple rectangular boundaries or complex polygonal shapes that precisely trace the contours of the site.
When defining a grid, the point spacing must be specified. The IES typically recommends a grid spacing that is no greater than one-fifth of the mounting height of the luminaires, though 10-foot by 10-foot spacing is a common standard for large commercial parking areas. Denser grids (e.g., 5x5 feet) provide higher resolution for identifying minimum points, but linearly increase calculation time.
It is crucial to align the calculation grid precisely with the grade elevation. If the site is a flat plane, the grid elevation should be exactly 0.0. If multiple tiered parking levels exist, separate calculation grids must be created at the corresponding Z elevations.
Defining Statistical Areas
A single large calculation grid covering the entire site may provide an overall average, but local ordinances often require specific metrics for distinct zones, such as the main parking area, pedestrian walkways, and building entrances. AGi32 allows users to draw statistical areas over the calculation grid to isolate metrics.
By defining polygonal statistical areas, the software calculates specific minimum, maximum, and average illuminance values, as well as uniformity ratios (Max/Min and Avg/Min) strictly within that boundary. This localized analysis is essential for demonstrating compliance with detailed specifications that demand higher illuminance near main entrances and lower baseline levels in peripheral parking zones.
Establishing Property Line Trespass Grids
Preventing light from spilling onto adjacent properties is a fundamental requirement of modern exterior lighting design. To quantify this, AGi32 requires the implementation of vertical calculation grids along the property lines.
These grids, often referred to as line grids or vertical planes, are placed exactly on the property boundary. The calculation points must be oriented facing inward toward the site to measure the incident light escaping the perimeter. Local codes typically dictate strict limits on vertical illuminance at the property line, often capping it at 0.5 footcandles or lower for adjacent residential zones. Accurately positioning these vertical grids is mandatory for generating compliance reports.
Strategic Luminaire Placement and Optimization
The layout of luminaires directly dictates the performance of the lighting system. Efficient pole placement minimizes fixture counts, reduces energy consumption, and ensures uniform light distribution while controlling glare.
Selecting and Defining Luminaires
Prior to layout, the appropriate photometric data must be loaded into the AGi32 luminaire definition dialog. This involves importing the IES file provided by the manufacturer and configuring key parameters. The wattage, lumen output, and specific light distribution type (e.g., Type III, Type IV, Type V) must be verified against the project specifications.
Crucially, the Light Loss Factor (LLF) must be applied at this stage. Exterior environments demand realistic depreciation calculations, combining Luminaire Dirt Depreciation (LDD) and Lamp/LED Lumen Depreciation (LLD). Failing to apply an accurate LLF will result in initial calculation values that do not represent the maintained illuminance required by code over the life of the installation.
Pole Placement Strategies
Initial pole placement should prioritize perimeter coverage and strategic interior locations that minimize interference with traffic flow and parking stalls. A common strategy is to utilize Type IV or forward-throw distributions along the perimeter, aiming light inward to maintain property line compliance while illuminating the edge parking spaces.
Interior areas are typically covered using back-to-back or quad-mounted Type III or Type V distributions on central poles. The mounting height of the luminaires is a critical variable; higher mounting heights generally improve uniformity and allow for wider pole spacing, but increase the potential for off-site glare and may be restricted by local zoning ordinances.
AGi32’s dynamic calculation engine allows designers to adjust pole locations and instantly view the impact on the calculation grid. This real-time feedback is invaluable for fine-tuning the layout. The goal is to achieve the required minimum illuminance without drastically exceeding the average targets, thereby maintaining optimal uniformity ratios and energy efficiency.
Aiming and Orientation
For standard parking lot luminaires, the aiming is typically straight down (nadir), relying entirely on the internal optics of the fixture to distribute light. However, in applications requiring floodlighting or specialized area lighting, the tilt and orientation (spin) of the luminaire must be precisely adjusted in AGi32.
The software allows for specific aiming angles to be defined. When utilizing tilted fixtures, designers must carefully monitor the potential for direct glare and increased light trespass, utilizing internal calculation tools to assess high-angle candela values that might cause visual discomfort to drivers or neighbors.
Executing the Calculation and Analyzing Results
With the site geometry, calculation grids, and luminaires accurately placed, the photometric model is ready for processing. The accuracy of the final output relies entirely on the precision of the preceding setup steps.
Full Radiosity Calculation vs. Direct Only
AGi32 offers two primary calculation modes. For simple exterior layouts without significant obstructions or building facades, a “Direct Only” calculation is often sufficient and significantly faster. This mode computes light traveling directly from the luminaire to the calculation point without accounting for reflections.
However, if the site includes large light-colored building facades, structural canopies, or complex architectural geometry, a “Full Radiosity” calculation is required. This engine simulates the inter-reflection of light off surfaces, providing a much more accurate representation of the final illuminated environment. When executing full radiosity, it is essential to ensure that appropriate reflectance values are assigned to the 3D surfaces (e.g., 20% for asphalt, 50% for concrete).
Reviewing Statistical Metrics
Upon completion of the calculation, the primary metrics must be analyzed against the project requirements. The standard IES RP-8-18 guidelines dictate specific minimum maintained illuminance levels and uniformity ratios (Maximum-to-Minimum) based on the activity level of the parking facility.
The designer must review the statistical summary in AGi32 to confirm that all criteria are met. If the minimum illuminance falls below the required threshold, localized adjustments—such as increasing a specific luminaire’s lumen package or adding a pole—are necessary. Conversely, if the maximum illuminance is excessively high, resulting in poor uniformity, wattage reductions or optic changes should be explored.
| Area Type | Typical Minimum Illuminance (fc) | Maximum Uniformity Ratio (Max/Min) |
|---|---|---|
| High Activity Parking | 0.5 to 1.0 | 15:1 |
| Medium Activity Parking | 0.2 to 0.5 | 20:1 |
| Low Activity Parking | 0.1 to 0.2 | 20:1 |
| Pedestrian Walkways | 0.5 to 1.0 | 10:1 |
| Property Line Trespass | 0.0 to 0.5 (Max) | N/A |
Advanced Troubleshooting and Optimization
Even with careful preparation, exterior photometric calculations often require iterative adjustments to address specific challenges or anomalies that arise during the analysis phase.
Addressing Light Trespass Violations
When vertical property line grids indicate illuminance values exceeding local ordinances, immediate corrective action is required. The first step is often to replace perimeter luminaires with more restrictive distributions, such as moving from a Type IV to a Type II, or utilizing fixtures with specialized “house-side” shielding optics.
If optic changes are insufficient, the physical location of the poles must be shifted further inward from the boundary. In severe cases, external shields or baffles may need to be specified for the luminaires, though this must be reflected in the photometric data used in AGi32 to ensure accurate calculations.
Mitigating Severe Uniformity Issues
Poor uniformity—characterized by extreme hot spots beneath poles and deep shadows between them—is a hallmark of suboptimal lighting design. This often occurs when high-lumen fixtures are mounted at low heights or spaced too far apart.
To resolve uniformity issues in AGi32, the designer should test alternative distribution types. A Type V distribution may create a severe hot spot, whereas a Type III distribution with wider lateral throw might bridge the gap between poles more effectively. Increasing the mounting height, if zoning permits, is another highly effective method for improving the Max/Min ratio across the site.
Managing Calculation Overloads
Massive site plans with hundreds of calculation grids and luminaires can strain system resources and significantly extend calculation times. To manage this, designers can optimize the model by reducing the density of calculation points in non-critical areas or temporarily disabling luminaires and grids that fall outside the immediate zone of interest.
Furthermore, ensuring that all 3D geometry is strictly necessary is crucial. Highly detailed 3D building models imported for aesthetic context rather than photometric reflection should be designated as “background” rather than calculation surfaces to prevent the radiosity engine from needlessly processing thousands of unnecessary mesh polygons.
Finalizing the Output and Reporting
The final phase of the AGi32 workflow is generating clear, professional documentation that communicates the calculation results to stakeholders, city planners, and electrical contractors.
Generating Isolines and Value Grids
Visual representation of the lighting distribution is critical. AGi32 allows users to generate isolines (contour lines of equal illuminance) overlaid on the CAD background. These isolines quickly illustrate the spread of light and help identify areas of high intensity or potential dark zones.
Additionally, the point-by-point value grid must be clearly visible, with the text sized appropriately for legibility when printed or exported to PDF. The software’s page builder tools allow the designer to arrange the site plan, calculation summaries, and luminaire schedules into a cohesive drawing sheet.
Exporting Data
Once the layout is finalized and compliance is verified, the calculated CAD background, complete with isolines, calculation points, and pole locations, can be exported back to DWG format for integration into the master project file. It is vital to ensure that the exported layers are organized cleanly so that the electrical engineer can easily reference the pole locations for conduit routing and circuit design.
A rigorous approach to the AGi32 exterior workflow, from meticulous CAD preparation to precise luminaire definition and strategic layout, ensures that the final photometric design is technically sound, highly efficient, and fully compliant with all regulatory requirements.
Common Mistakes and Troubleshooting
Deviating from a structured methodology often introduces subtle errors into the photometric model. Identifying and correcting these common mistakes is essential for maintaining accuracy.
Incorrect Z-Axis Import Scaling: Bringing a civil drawing into AGi32 with mismatched units (e.g., inches instead of feet) drastically alters the site dimensions. Always verify the coordinate scale immediately after import by using the measuring tool across a known distance, such as a standard 9x18 foot parking stall.
Neglecting Light Loss Factors: Calculating exterior grids using initial lumens (LLF = 1.0) guarantees that the real-world installation will fall below the required illuminance levels as the fixtures age and accumulate dirt. Always apply a calculated LDD and LLD to ensure maintained compliance.
Overly Dense Calculation Grids: Placing points at 1-foot intervals across a massive parking lot provides no statistical advantage over a standard 10-foot grid but geometrically increases software processing time. Reserve high-density grids for small, critical task areas like ATM drive-throughs or specific pedestrian crossings.