3D assets → Google Earth
See it standing
before you build it.
Enter two numbers. PylonForge builds the machine and drops it onto real terrain, true to scale, in Google Earth.
LIVE 3D MODEL
LIVE 3D MODEL ON A REAL SITE · SAME MESH AS EXPORT
1:1
True-scale placement
< 10s
Model to Google Earth
12
Parametric asset types
1 model, 300 turbines
Shared geometry, no duplicate files
Scroll to fly in
HOW IT WORKS
From spreadsheet to standing on-site.
One pipeline, no modeling software. Rows go in, validated geometry comes out, placed on real terrain.
01 · INPUTCSV or form
namelatlonhub_mrotor_m
T-0139.7392-105.211098116 ✓
T-0239°44'21"N105°12'40"W98116 ✓
T-0339.7401-105.2089312116 !
DMS or decimal — both parse. Out-of-range rows get flagged, never silently dropped.
02 · GEOMETRY ENGINEprocedural
wind_turbine.build({ hub: 98, rotor: 116 })
airfoil blades · lofted meshZ-up · meters300 identical turbines → 1 .dae
03 · GOOGLE EARTH.kmz
39.7392°N · 105.2110°WrelativeToGround
KMZ✓
wind-site.kmz
KML folders per type · one <Model> per asset
LIVE REBUILD
0 triangles · rebuilt in 1.0 ms
drag to orbit
PARAMETRIC SANDBOX
Drag. The engine rebuilds.
Pick an asset. The parameters you'd type into a project rebuild the mesh instantly — every derived dimension recomputes.
100 m
116 m
158 m
Total tip height
58 m
Blade length
10,568 m²
Swept area
72.9 m/s
Tip speed @ 12 rpm
Identical math writes your COLLADA — the preview and the export can't disagree.