rescape

CAD context guide

Create a CAD site-context model from open geographic data

Draw a project boundary, choose useful context layers and export a layered DXF with terrain, buildings, roads and water.

Useful for

Architects, landscape designers, urban designers, students and CAD users

You will make

A true-scale, locally positioned DXF that you can edit as project context in AutoCAD, Rhino, Vectorworks or another DXF-capable application.

Finished CAD context model of Manhattan showing terrain, buildings and roads

From boundary to CAD

  1. 1

    Define only the context you need

    Open the example below or draw your own rectangle, polygon, circle, rounded rectangle or arc. Keep the boundary close to the project: smaller files generate faster and remain easier to edit.

    If you already know the bounds, expand Coordinates and enter west, south, east and north directly.

  2. 2

    Choose DXF and review the layers

    Use the Config panel to select DXF and include the context that matters: buildings, terrain, roads, water, land use and vegetation. Remove layers you will not use before generating the file.

  3. 3

    Check area, price and data expectations

    The Stats panel shows the selected area and price before submission. Small regions are free, which is useful for checking local coverage before requesting a larger site.

  4. 4

    Generate and download the DXF

    Sign in, submit the job and keep the job page open while the sources are fetched and assembled. Download the DXF after the job reaches Succeeded.

  5. 5

    Import, organize and verify

    Open or import the DXF using the units shown in the job configuration. Keep the named layers separate, compare the model with a current reference, then simplify or restyle it for the drawing you are producing.

    Treat source-derived heights and outlines as context. Replace critical geometry with surveyed or project-authoritative information.

Open-data limits

Check the context before you design against it

  • Building footprints may be missing, generalized or stale, and height attributes are incomplete in many places.
  • Terrain resolution depends on location: regional lidar is used where configured and available, with lower-resolution global fallbacks elsewhere.
  • Roads, water, vegetation and land-use boundaries come from open datasets and may not match current site conditions.
  • The output is intended for context, visualization and modelmaking—not surveying, engineering or construction documentation.

Regions that demonstrate this workflow