CSV import & coordinates

If your site already lives in a spreadsheet, don't re-type it. Each asset type has a CSV template whose columns match its form fields — fill it, upload it, and the whole layout appears in 3D.

01
Download the template
In the project editor, open Import CSV and pick the asset type. The template has one column per field — label, latitude, longitude, heading, and the type's dimensions.
02
Fill in your rows
One row per asset, in Excel, Google Sheets, or anything that saves CSV. Coordinates can be decimal or DMS — mix freely.
03
Upload and review
Every row is checked before anything saves. You get a per-row report: valid rows ready to import, invalid rows with the exact reason (bad coordinate, missing dimension, out-of-range value).
04
Import the valid rows
Confirm, and the valid rows become assets in the project. Fix the flagged rows in your spreadsheet and upload again — nothing is ever silently dropped.

Coordinate formats we accept

Anywhere PylonForge asks for a coordinate — forms or CSV — these all work:

→Decimal degrees: 41.1398, -104.8202
→Degrees-minutes-seconds: 41°8'23.4"N or spaced, 41 8 23.4 N
→Colon-separated: 104:49:12.7W
→Hemisphere by letter (N/S/E/W) or by sign — south and west are negative

Watch the sign on longitude: everything in the Americas is west, so decimal longitudes there are negative (-104.82, not 104.82). A site that lands in the ocean on export almost always has a dropped minus sign.

Limits and tips

→One asset type per upload — importing turbines and a met tower is two quick uploads.
→A 100-row layout is routine; the whole-site 3D view handles it.
→Keep labels unique-ish (T-01, T-02…) — they become the placemark names you'll see in Google Earth.