Boundary file requirements
How to draw and name the features in a Google Earth file, and how the Clean boundary review reads the file when you load it.
Every Google Earth file goes through the same reading when you load it. The application looks for the plots, the areas to keep clear, the lines to keep a corridor around, and any pins. A file that already fits that shape loads straight away. A file with anything to decide opens the Clean boundary window, which shows what it found and saves a clean copy.
That makes file preparation the highest-leverage half hour in the whole design. A well-drawn file lays out in one run, with no questions asked.
The same rules are available inside the application, from the ⓘ button beside Browse… on the Input Boundary File card — see The preparation guide inside the application.
The plant boundary
| Requirement | Detail |
|---|---|
| Geometry | A closed polygon. |
| Closure | The first and last coordinate of the ring must be identical. |
| Name | Anything you can recognise. Each plot becomes one plant, with its own column in the Summary view. |
| Position | Top level. A polygon that is not inside another polygon is a plot. |
| Count | One or many. Several plots in one file are laid out as a multi-plot site in a single run. |
A polygon inside a plot is an area to keep clear. So everything you want kept clear — water, buildings, transmission lines — belongs inside the plot it affects. A polygon drawn clear of every plot is read as another plot and gets tables of its own, unless its name marks it as water, in which case it is listed as Outside the plots, not used.
In Google Earth that means one filled shape for the fence line, drawn with the polygon tool, and every pond, building and line placed visibly inside it before you save.
Preparing the file
Draw the plant boundary as a polygon
Trace the fence line. Close the ring back onto its first point. If your source is a survey with a coordinate schedule, enter the last coordinate as a repeat of the first rather than relying on the drawing tool to close it for you.
Draw every exclusion inside that boundary
One polygon per water body, building, substation, borrow pit or graveyard. One line per transmission line, canal, drain or road.
Name each feature so you can recognise it
The name appears on the Site tab and in the review, and it sets whether the
feature starts as water. Use a word from the list below for water —
Pond 3, Nala south — and any clear name for the rest.
Save the file and load it
Save as .kmz or .kml, then load it with Browse… on the Site tab. If
there is anything to decide, the Clean boundary window opens — see
The Clean boundary review below.
Water
An area or a line is either water or it is not. The shape decides whether it is an area or a line; the name sets whether it starts as water. A whole word in the name has to match, in any case:
| Water words |
|---|
| pond, lake, reservoir, water, waterbody, wetland, swamp, marsh, talab, talav, tank, pokhar, canal, channel, drain, drainage, nala, nalla, nallah, nullah, river, stream, creek, flood |
| Feature name | How it starts |
|---|---|
Pond 3 | Water |
WATER BODY - north | Water |
Nala south | Water |
Drainage tank | Water |
P3 | Not water |
Excl-04 | Not water |
Pondicherry store | Not water: pond is only part of a word |
Among areas and lines that are not plots, water is the only difference the name makes. A water feature and any other feature keep tables out in the same way, but only water is drawn and booked as water. You can change it for any feature with the Water tick in the review, which Review boundary… on the card opens at any time.
Water bodies are read only from what you draw in the file. The application does not look for water in satellite imagery, so a pond you did not draw does not exist as far as the layout is concerned.
Draw a polygon at the water's maximum extent, not the extent on the day the imagery was taken. To keep a margin around it, use the Area setback on the Site tab.
Obstructions and buildings
Anything that occupies ground but is not water is a plain obstruction: existing buildings, a substation compound, a temple, a graveyard, a rock outcrop, a borrow pit.
- Draw a closed polygon, inside the plant boundary.
- No table is placed on it, nor within the Area setback around it.
If you discover an obstruction after the layout has been generated, you do not have to go back to the file: obstructions can be drawn directly on the plot. See Obstructions and exclusions.
A polygon inside another whose name uses a word such as plot, block, phase
or survey, or that still has Google Earth's own name such as Untitled Polygon,
is not assumed to be an obstruction: the review asks you which it is.
Lines
Transmission lines, canals, drains, roads and railways are line features, not polygons. A line has no width in the file, so the width kept clear around it comes from the Site tab.
- Draw the feature as a line through the site. Drawing it as a thin polygon instead means it is read as an area and only the strip you drew is kept clear.
- Every line that is not a plot becomes a corridor. The name does not change the width.
- A line up to 500 m from a plot is kept, because a corridor can reach that far. A line further away is listed as Outside the plots, not used.
Corridor and setback widths
| Field | Default | Range | What it does |
|---|---|---|---|
| Line corridor (each side) | 15.0 m (30 m corridor) | 0.0–500.0 m | No tables within this distance of a line |
| Area setback | 0.0 m | 0.0–100.0 m | No tables within this distance of an area. At 0 tables can go up to its edge |
Once a file is loaded, each line and each area gets its own row under these fields, so a nala and a 220 kV line can have different widths. Changing the common field moves every row still at the old value; a row you edited keeps its own. See Site parameters.
| Line corridor per side | Corridor cleared |
|---|---|
| 15.0 m — the default | 30 m |
| 30.0 m — the application's own suggestion for a 400 kV line | 60 m |
Set a transmission line's corridor to match the right-of-way the utility imposes on your site, since that is a statutory figure rather than a design choice. For a road, enter half the road's width: a 5 m road takes 2.5 m each side.
Two drawing habits save trouble:
- Draw one continuous line across the site, rather than several short segments end to end. A single line gives one continuous corridor and one row on the Site tab.
- Run the line right out through the boundary edge. A line that stops short of the fence leaves a wedge of usable ground at each end, and tables get placed in it — directly under the conductor.
Pins
A pin marks a point. It is a label only unless you keep it in the review, where it becomes a small spot with no tables. A pin inside a plot opens the review so you can decide. A well or a tower you want kept clear is better drawn as a small polygon.
Multiple boundaries in one file
One file can carry as many plots as the site has, and all of them are laid out in a single run.
- Each plot becomes its own plant. It gets its own column in the Summary view, its own area and capacity, and its own blocks in the package's Google Earth file. A Total column aggregates every plant.
- A feature belongs to the plot that contains it. A pond drawn inside plot 3 is subtracted from plot 3.
- Plots must not overlap. Touching along a shared edge is fine. If two overlap, the review asks how to resolve it.
- Draw every plot, even the small ones. Adding a plot later means editing the file and loading it again, because the boundaries come from the file and cannot be drawn on the plot.
What follows from a multi-plot file — one main control room, a unit substation in each of the other plots, and medium-voltage cables between them — is covered in Multi-plot sites.
What each feature does to the layout
Once the file is read, the features are used in a fixed order:
- The latitudes and longitudes are converted to metres in the site's local UTM zone.
- Each plot is shrunk inward by the Perimeter road width to give that plant's usable area.
- Areas are subtracted from it, with their setback.
- Every line is buffered into a corridor, and that corridor is subtracted too.
- Excluded terrain is subtracted, when topography is enabled.
Module tables are then placed only where they fit entirely inside what is left, which is why a polygon drawn slightly too small still leaves tables overhanging the real obstacle, and a polygon drawn generously does not. See How placement works.
Quick reference
| Feature | Draw it as | Name |
|---|---|---|
| Plant boundary | Closed polygon, first coordinate = last, not inside another polygon | Any name; it becomes the plant name |
| Water body | Closed polygon inside a plot | A water word |
| Building, substation, other obstruction | Closed polygon inside a plot | Any name without a water word |
| Canal, drain, nala | Line inside a plot | A water word |
| Transmission line, road, railway | Line inside a plot | Any name without a water word |
Common mistakes
| Mistake | What happens | Fix |
|---|---|---|
| The boundary is drawn as a line or a path | With no name, Google Earth's own name or a word such as boundary or plot, and ends within 50 m of each other, the review offers to close it. Any other line is read as a line to keep clear, not as a plot. A file with no plot gives Boundary read error: "The file has no plot: draw the site boundary as a closed polygon." | Redraw it as a closed polygon, or close it in the review |
| The boundary is drawn in several pieces | If the pieces meet within 50 m, the review offers Join into one plot | Join them in the review, or redraw as one polygon |
| A polygon's ring is not closed | Generate Layout opens the Check boundaries window — see below | Repeat the first coordinate as the last, or redraw the polygon with the drawing tool's own close action |
| An obstruction is drawn clear of the boundary | It is read as another plot and gets tables | Move the polygon inside the boundary, or extend the boundary to contain it |
| Two plots overlap | The review offers to merge them, cut the overlap out of one, or remove one | Choose in the review, or edit the polygons so they touch at most along an edge |
| A water body has no water word in its name | Tables are kept off it, but it is not drawn or booked as water | Tick Water in the review, from Review boundary… on the card, or rename it |
| A transmission line is drawn as a thin polygon | It is read as an area, so only the strip you drew is kept clear | Redraw it as a single line and let the corridor do the work |
The Clean boundary review
The review opens when the file has something to decide, and from Review boundary… on the card at any time after a Google Earth file is loaded. It opens by itself for:
- a boundary drawn as an open line or in pieces, an outline that crosses itself, a duplicate, an overlap, or a polygon drawn inside another that may be the plot;
- a pin inside a plot;
- a CAD export saved as loose lines;
- a village survey map, where you pick your parcels;
- a finished layout opened as a boundary;
- a field survey saved as points only, where the application traces the boundary and asks what each unknown code is.
Save clean KMZ and load writes <your file>_clean.kmz beside the original and
loads it. The original is not changed. Cancel leaves the file unloaded, and
whatever was loaded before stays loaded.
The window, its choices and each of these cases are on Clean boundary.
When a boundary fails the check
If a polygon's ring is left open by more than about 11 m, Generate Layout opens the Check boundaries window. A warning banner at the top reads 2 boundaries have a problem — or 1 boundary has a problem — with the detail Leave them out and continue with the others, or fix them in Google Earth and load the file again.

Under the banner is a table with the columns Leave out, Boundary and Problem. Each problem is spelled out with its size, for example Ring is NOT CLOSED (gap between first and last point ≈ 42.7 m) — a small gap is a drawing tool that did not snap back to the first point; a large one is a boundary that was never closed at all. Leave out is ticked by default on every row, and the note under the table says what an untick means: An unticked boundary is kept as it is and may produce a wrong layout.
The footer offers four buttons:
| Button | What it does |
|---|---|
| All | Ticks Leave out on every problem boundary |
| None | Unticks every row, so every boundary is kept as drawn |
| Fix in Google Earth first | Ends the run without generating. Correct the geometry in Google Earth, save, and load again |
| Continue without 2 | Generates with the ticked boundaries left out. The number follows the ticks; when nothing is ticked the button reads Continue with all boundaries |
Leaving the problem boundaries out is the right answer when one plot of a twelve-plot file is malformed and you want to see the other eleven now.
A boundary left out is not a deferred boundary. It contributes no area, no capacity and no column to the Summary view, and it does not appear in any export. If you leave one out and then read the total capacity, you are reading the total for a smaller plant than the one you intend to build.
The preparation guide inside the application
The ⓘ button beside Browse… opens the KMZ File Preparation Guide: an introductory paragraph, then the sections 1 ▸ Plant / Site Boundary, 2 ▸ Water Bodies (Ponds, Lakes, Canals …), 3 ▸ Transmission Lines (TL) / Canals / Roads, 4 ▸ Buildings / Obstruction Areas and 5 ▸ Common Mistakes to Avoid, and a Quick Reference table with the columns Feature, KML type, Name rule and Colour on map. One Close button returns you to the Site tab.

The guide lists the most common water words. The full list is on this page.
Where to go next
Which boundary file to use
The three input types compared, and how to load one
Clean boundary
The review a file goes through on loading, survey maps and field surveys included
Multi-plot sites
What changes when one file carries several boundaries
Obstructions and exclusions
Adding exclusions after the file is loaded
Which boundary file to use
The three kinds of boundary file the application accepts, what each one carries, and how the Input Boundary File card on the Site tab reads them.
Clean boundary
The review every Google Earth file goes through on loading, and what to do with open lines, overlaps, survey maps, finished layouts and field surveys.