Contour lines
for Rhino
Real contours as a DXF: polylines at their elevation, in metres, ready for a surface, Grasshopper or the laser.
Curves
at their height
Rhino Polylines at their elevation, in metres, one layer per contour type.
What's in
the file
- 01
At their real height
Every contour is a 3D polyline, with its elevation on each vertex.
- 02
One layer per type
Index, intermediate, half-interval and coastline, ready to freeze or recolour.
- 03
In your coordinate system
UTM, Lambert-93, British National Grid… X, Y and Z all in metres.
- 04
Source in the file
Dataset, licence, interval and CRS in the header. R12, read by every CAD app.
999 TopoLines (https://topolines.app) 999 generated 2026-11-05T09:56:26.874935+00:00 999 contour interval 10 999 CRS EPSG:2154 — RGF93 / Lambert-93 999 author TopoLines 999 terrain IGN RGE ALTI 2 m 999 attribution Elevation: © IGN — RGE ALTI® (Etalab 2.0) 0 SECTION 2 HEADER 9 $ACADVER 1 AC1009
999
TopoLines (https://topolines.app)
999
generated 2026-11-05T09:56:26.874935+00:00
999
contour interval 10
999
CRS EPSG:2154 — RGF93 / Lambert-93
999
author TopoLines
999
terrain IGN RGE ALTI 2 m
999
attribution Elevation: © IGN — RGE ALTI® (Etalab 2.0)
0
SECTION
2
HEADER
9
$ACADVER
1
AC1009From map
to file
Search a place or coordinates and frame the zone. The finest open data covering it is picked for you.
From 5 to 100 m, with an index contour every Nth line. The preview redraws as you go.
Pick DXF and a metric coordinate system, then download.
In Rhino
and Grasshopper
Set the model units to metres when Rhino asks.
Import. The layers come through as Rhino layers.
Surface or mesh. Patch or MeshPatch through the curves.
Grasshopper. Divide the curves, feed Delaunay Mesh.
Elevation data
Sharper
where the data is
National 5–10 m models where they exist, a global bare-earth model everywhere else.
Bare earth first
Contours follow the ground, not treetops or rooftops.
Picked for your zone
Auto reads the finest source covering the whole zone.
Bring your own
Upload a georeferenced GeoTIFF and trace it like any zone.
Credited in the file
Source and licence are written into every export.
Frequently asked questions
Formats, coordinates, data and pricing. More in the exports documentation.
Do the curves keep their elevation in Rhino?
Yes. They are 3D polylines with the elevation on every vertex, so they sit at their real height and can drive a surface or a mesh directly.
Why is the model so far from the origin?
A metric coordinate system places the site at its real-world coordinates. Move it to the origin after import, or keep it in place if other site data shares the same system.
Can I use it for a laser-cut terrain model?
Yes. Each elevation is its own curve: project a level to the construction plane and cut it, one sheet per interval. SVG is also available, with the paths grouped by elevation.
What is the finest data available?
National lidar where it exists: down to 0.5 m in Switzerland and 1 m in France, the US and England, picked automatically for small zones. Elsewhere, the GEDTM30 30 m bare-earth model.
Is the export free?
No. The free account exports PNG; DXF, GeoJSON and SVG cost 1 credit for a zone under 10 km² (3 with national lidar). Packs start at €5 for 20 credits, never expire, no subscription.
What can't it do?
Replace a survey. The finest interval is 5 m, and the contours come from bare-earth terrain models: accurate to within a few decimetres to about a metre with national lidar, to a few metres with the 30 m worldwide model. A vector export covers up to 500 km² per zone.