"I don't want to see your plans, Maya," he’d said, pushing a pair of cheap VR goggles across the table. "I want to stand on the ridge and see the sunrise hit the infinity pool. Can you put your AutoCAD into Google Earth?"
The export was the devil. She tried exporting a 3D DAE (Collada) file, but the resort’s sleek modernist walls came out looking like melted cheese. She tried an KMZ export, but the terrain of Google Earth Pro swallowed her swimming pool whole, burying it ten meters under a virtual hillside. autocad to google earth pro
Maya Vasquez was a perfectionist. For twenty years, she had made her living drawing crisp, unyielding lines in AutoCAD. Every wall had a layer, every pipe a color code, every contour line a mathematically precise elevation. Her world was one of Object Snaps (OSNAP) and absolute coordinates. There was no room for "close enough." "I don't want to see your plans, Maya,"
The next morning, her phone buzzed. A video from the client. He was using his VR headset, standing (virtually) on the ridge she had drawn. The sun was rising over her pool. He was crying. "It's like I'm already there," he whispered. She tried exporting a 3D DAE (Collada) file,
The virtual sun rose over the digital Andes. Long, pixelated shadows stretched from her wireframe cabanas. The light caught the face of the 3D extrusion she’d given the main lodge. For a moment, the messy quilt of satellite photo and the sterile precision of CAD merged into something that looked real. Not a map. Not a drawing. A place .
For three weeks, Maya became a cartographer. She stripped her massive DWG file down to its skeleton: just the site boundary, the building footprints, and the access road. She used the GEOGRAPHICLOCATION command, feeding in the exact lat/long of the Andean valley. AutoCAD hummed, accepted the coordinates, and drew a faint, glowing north arrow. Step one was done.