She needed a different approach.
"It's on Google Earth," Mr. Verona had chirped over the phone. "I drew the trails, the lodge, and the helipad right on the satellite image. Just… put it into your CAD thing, okay?"
Then, she tried the import again, but this time she used and chose the KML as a source. A dialog box appeared—a wise, wrinkled old wizard compared to the brute force of before. She told AutoCAD to use the current geographic coordinate system. She told it to interpret lines as polylines and polygons as closed boundaries. autocad import kml
She knew the enemy now: projection. Google Earth used WGS84, a geographic coordinate system based on latitude and longitude on a sphere. Her drawing was set to State Plane, a grid designed to minimize distortion over a small area. The KML had been flattened like a pancake, and all the juicy terrain data had squirted out the sides.
She emailed the DWG back to Mr. Verona. An hour later, her phone buzzed. She needed a different approach
First, she established the truth. She used GEOGRAPHICLOCATION to pin the drawing to the real world, importing the same satellite imagery as a live map backdrop. Now, AutoCAD knew it was in the same universe as Google Earth.
She didn't just trace lines. She added contour labels, adjusted the trail slopes to meet ADA compliance, and calculated the exact cubic yards of earth needed to level the helipad. She added a polite note in the margin: "Helipad bearing adjusted 2.3 degrees east to align with prevailing wind. Trails optimized for drainage." "I drew the trails, the lodge, and the
The first attempt was a massacre.