TopoExport vs Shapezo: A Practical Data Pipeline for 3D Terrain

TopoExport and Shapezo serve distinct purposes in a 3D terrain workflow. TopoExport transforms elevation data into a 3D surface, while Shapezo uses a selected map area as the boundary for an AI-generated model. The choice between them depends on whether one is validating height data or establishing a spatial context.

For TopoExport, the input contract is clear: elevation grid, contours or another terrain source, coordinate system, unit, boundary, and desired output format. Before generating a surface, the source resolution, vertical datum, and boundary are recorded if available.

Shapezo's input contract begins with geographic scope. Selecting a rectangular area on a map guides the system on which region to interpret, preventing the generated model from drifting into an undefined scene. The output can include both terrain and built context, but the boundary remains the most crucial input.

Terrain errors often arise from unnoticed assumptions. TopoExport requires verification of the source's coordinate system—whether it uses geographic coordinates or a projected system—and whether vertical values are in meters or feet. For Shapezo results, the map extent and the source context used for generation should be documented.

The AI model's precision should not be assumed to match that of a Digital Elevation Model (DEM); it is treated as a spatial reference requiring comparison with authoritative data before integration into a measured workflow.

When starting with Shapezo, if the site is unfamiliar, begin with a large enough box to encompass the terrain feature and nearby access network. Rotate the result and mark relationships to test, such as a ridge above a road or a slope between public spaces. This initial pass is not a substitute for terrain processing but a means to narrow the focus. Rather than exporting the entire region due to uncertainty about the important landform's location, use the generated context to define the next boundary.

Once the relevant area is identified, bring the best available elevation source into TopoExport. Set the boundary, confirm the units, and select a mesh resolution that matches the purpose. For presentation terrains, a lower density may suffice, while surfaces intended for grading reviews or 3D printing require higher density. Create separate versions when necessary: a neutral surface for slope checking and a visually exaggerated version for explaining relief. Keeping these versions distinct avoids conflating communication settings with measured conditions.

A short validation pass is essential before handoff. Compare one known horizontal distance, one known elevation difference, and inspect the boundary for clipping or missing continuation. Check the exported file in the next tool, not merely the source viewer. Save the source name, date, unit, coordinate system, and settings.

This pipeline maintains clear roles. Shapezo answers, "What part of the place should I study?" TopoExport answers, "What does the terrain surface look like when I use the elevation data I trust?" Neither workflow should be presented as inherently more precise than its inputs.