Blender to Google Earth

    1

    Georeference and fuse Blender 3D models into Google Earth Pro with optimized roads and terrain-adaptive site redlines.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    blender-to-google-earth

    Example session with this skill installed

    I have a blender file at ./models/site_plan.blend. I need to export the 'Phase_1_Buildings' collection to Google Earth using UTM zone 50N and origin (456000, 3821000). Fix any road gaps.

    • Read your context and instructions
    • Compiled the blender-to-google-earth

    I have scanned the Blender scene and initialized the export pipeline for the 'Phase_1_Buildings' collection. I applied a UTM 50N projection with the specified offsets and processed the road geometry using draped polygons to prevent Z-fighting.

    Export Summary

    ComponentStatusResult/Path
    Blender ScanPASS12 unique meshes found in Phase_1_Buildings
    DAE ExtractionSUCCESSCollada files generated with baked transforms
    Road ProcessorOPTIMIZED4 thick-mesh roads converted to clampToGround polygons
    GeoreferencingVALIDATEDApplied UTM 50N (E: 456000, N: 3821000)
    Output KMZGENERATED./exports/phase_1_final.kmz
    
    # Generated Project Configuration Snippet
    project_name: site_plan_export
    crs:
      utm_zone: 50
      hemisphere: N
      utm_offset: [456000, 3821000]
    layers:
      - name: Phase_1_Buildings
        type: model
        double_sided: true
      - name: Site_Roads
        type: draped_polygon
        subtract_previous: true
    

    Next steps

    1. Open ./exports/phase_1_final.kmz in Google Earth Pro to verify architectural placement.
    2. Run python3 ./scripts/b2ge_cli.py verify --kmz ./exports/phase_1_final.kmz --launch-ge for a full QA report.
    3. If redlines appear broken on the hillside, re-run with redline_processor.py using a 2.0m interpolation step.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Converting complex 3D planning models from Blender to Google Earth Pro often results in broken road geometry, disappearing redlines on sloped terrain, and misaligned coordinate systems. This skill provides a modular, production-tested toolchain to automate the extraction, georeferencing, and optimization of architectural assets into clean KMZ files.

    What it does

    • Geospatial Registration maps Blender local coordinates to WGS84/UTM using offsets, control points, or lon/lat anchors.
    • Mesh Optimization bakes rotations and scales into local vertices while handling collection instances for clean DAE exports.
    • Road Geometry Repair replaces disjointed 3D meshes and thick curbs with KML clampToGround polygons to eliminate Z-fighting and gaps.
    • Redline Enhancement prevents site boundaries from clipping into terrain at low angles using interpolated 3D paths and altitude offsets.
    • Integrity Verification runs SHA256 checksums on assets to ensure partial updates don't corrupt existing architectural data.

    How it works

    1. Scan the Source: Use the scan command to analyze .blend collections and mesh structures before extraction.
    2. Configure Project: Populate a YAML configuration with UTM offsets, target layers, and interpolation steps.
    3. Execute Pipeline: Run the build, road, or redline commands to process specific layers into georeferenced KMZ.
    4. Automated QA: Run the verify command to check for missing textures, orphaned files, and coordinate consistency.

    Frameworks & tools

    Built for Python 3 with PyYAML and Shapely. Integrates with the Blender API (bpy, bmesh) for headless extraction and Google Earth Pro for final visualization.

    Why this beats prompting it yourself

    Generic AI lacks the specific spatial logic required to prevent KML redline flickering or to calculate UTM-to-local vertex transformations correctly. This skill applies project-hardened geometric rules, such as boolean difference operations for road overlays, that standard prompts ignore.

    Use cases

    • Exporting architectural site plans to Google Earth for stakeholder presentations.
    • Fixing broken or floating road geometry in existing large-scale landscape KMZs.
    • Optimizing survey redlines to remain visible on steep hillside terrain.
    • Performing surgical updates on single buildings within a master plan KMZ.

    Known limitations

    Requires a local Blender installation for extraction tasks. Does not support high-precision survey-grade output without external surveyor-verified control points.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires local Blender installation for script execution. Cannot guarantee survey-grade accuracy (millimeter level) without certified physical control points. GUI verification requires GE Pro.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the georeferencing process, converting Blender’s local coordinates to WGS84/UTM while fixing common visual bugs like Z-fighting on roads and flickering site redlines on sloped terrain.

    The package includes the production-tested toolchain, a collection of modular processing commands (build, road, redline), and a template YAML configuration to map your project’s spatial data.

    It is designed for Python 3 environments and integrates with the Blender API (bpy/bmesh); it works best with AI agents capable of executing local CLI commands and managing file system operations.

    Yes, the skill includes a 'verify' command that uses SHA256 checksums to ensure that when you update a specific building or site layer, the rest of your master plan KMZ remains intact and uncorrupted.

    While the tool provides robust georeferencing via UTM offsets and control points, the final accuracy depends on the quality of your source anchors and local Blender installation.

    New in Agents & Orchestration

    Free