This article describes how to import a Google KMZ or KML file.
TABLE OF CONTENTS
- Importing a Google Earth KMZ or KML
- Expanding the aerial imagery
- Creating keep out areas
Importing a Google Earth KMZ or KML
Importing boundaries from KMZ or KML files need to be set up as polygons. Boundaries set up as paths will not be recognized in SunDAT Web.
- Select the Project icon and then press the Import KMZ/KML/DXF/DWG button
- Select the KMZ or KML to import into SunDAT Web. Then press Open to begin the import process into SunDAT Web
- After the import is complete, boundaries from the KMZ/KML will be visible in the model and assigned as Regions automatically. Also, project information in the Project Setup will be updated with information from the KMZ/KML and an aerial imagery will be shown behind the region.
Expanding the aerial imagery
Sometimes boundaries imported from KMZ or KML will be larger than the aerial imagery. In this case, the aerial imagery can be enlarged in Project Setup.
- Go to Project -> Site
- Scroll down Imagery Radius(meters). Expand the aerial imagery by either adjusting the toggle bar or entering a value
- Press the Update button and the project will update with the aerial imagery expanded
Creating keep out areas
For SunDAT to recognize keep out areas, polygons in the KMZ/KML need to be assigned as keep outs in Google Earth before importing into SunDAT Web.
- In Google Earth, expand the KMZ/KML in Places tray to see the object structure
- Select the polygon that is to be the keep out area. Right-click it and choose rename.
- Rename the polygon keep out
- If there is more than one keep out area, repeat the same steps above
- Save the place as a KMZ/KML file
- Import the KMZ/KML into SunDAT Web and the keep out region will appear as a red region
What is the source of the aerial imagery and terrain?
SunDAT Web uses Mapbox
Can import more than one KMZ or KML into a SunDAT Web project?
No. The easiest way for multiple KMZ or KML files is to import them together in Google Earth and then export that as a single file.
Failed KMZ or KML import
Error Message: ERROR IMPORTING KML: NO POLYGONS FOUND IN KMZ
SunDAT requires polygons in order to import to import a KMZ or KML file. The reasons why SunDAT cannot find polygons in the KMZ or KML could be because
- The KMZ or KML file only contains paths and not polygons
- The polygons have no names or incompatible characters in the name
If the KMZ or KML has polygon(s), but it is not importing into SunDAT, double check the polygon(s) has a name(s) or rename the polygon(s) if there are special characters
- Open the KMZ or KML file in Google Earth
- Expand the KMZ or KML file in the Places window to see the folder structure
- Look for the polygon(s) in the KMZ or KML and if it has [no name], rename the polygon by right-clicking the polygon and selecting Rename
If the site boundaries in the KMZ or KML are paths, then they will need to be changed to polygons. The quickest way to convert a path to polygon is to open the KML file in a text editor and making a few edits
- [If the file is a KML, skip down to step 4] For a KMZ, it will need to be converted to a KML for the file to be edited in a text editor. Open the KMZ in Google Earth
- Right-click on the KMZ in the Places window and select Save place as...
- In the save file window, change the Save as type: to KML (*.kml) and then save
- Open the KML file in a text editor either from the text editor or right-clicking the file and selecting Open with and then choosing the text editor
- In the text editor, find a replace <Linestring>with <Polygon><outerBoundaryIs><LinearRing>. Also, find and replace </LineString> to </LinearRing></outerBoundaryIs></LinearRing>
Error Message: ERROR IMPORTING KML: INVALID DATE/TIME IN ZIP ENTRY INVALID DATE/TIME IN ZIP ENTRY UNDEFINED PREFIX XSI FOUND
In the KMZ/KML, there is a "XSI" prefix to an XML attribute that is throwing an error on import