Help with 3D: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (→‎Example: fix url)
(use cmd template)
Line 1: Line 1:
== Raster 2.5D Surfaces ==
== Raster 2.5D Surfaces ==


This is the "typical" case, and most [http://grass.itc.it/grass63/manuals/html63_user/raster.html GRASS r.* modules] work in this mode. The GIS layer is defined by north,south,east,west and the raster map's cell values represent the elevation.
This is the "typical" case, and most {{cmd|raster}} (GRASS r.* modules) work in this mode. The GIS layer is defined by north,south,east,west and the raster map's cell values represent the elevation.


* [http://grass.itc.it/grass63/manuals/html63_user/rasterintro.html An introduction to raster processing in GRASS GIS]
* {{cmd|rasterintro}}: An introduction to raster processing in GRASS GIS


Snippet from the [http://en.wikipedia.org/wiki/2.5D Wikipedia definition] for 2.5D: "The idea is that the program's canvas represents a normal 2D painting surface, but that the data structure that holds the pixel information is also able to store information regarding z-index (depth) as well as other information such as material settings, specularity, etc. With this data it is thus possible to simulate lighting, shadows, and so on."
Snippet from the [http://en.wikipedia.org/wiki/2.5D Wikipedia definition] for 2.5D: "The idea is that the program's canvas represents a normal 2D painting surface, but that the data structure that holds the pixel information is also able to store information regarding z-index (depth) as well as other information such as material settings, specularity, etc. With this data it is thus possible to simulate lighting, shadows, and so on."
Line 9: Line 9:
Horizontal (2D) region settings are handled by the ''g.region'' module. The third dimension is unbound.
Horizontal (2D) region settings are handled by the ''g.region'' module. The third dimension is unbound.


2.5D rasters may be visualized in 3D with GRASS's [http://grass.itc.it/grass63/manuals/html63_user/nviz/index.html NVIZ] program, or as a shaded relief in 2D space with the [http://grass.itc.it/grass63/manuals/html63_user/r.shaded.relief.html r.shaded.relief] module.
2.5D rasters may be visualized in 3D with GRASS's {{cmd|nviz}} program, or as a shaded relief in 2D space with the {{cmd|r.shaded.relief}} module.


==== Screenshots ====
==== Screenshots ====


:http://grass.itc.it/grass61/screenshots/images/srtmV2_trento_small.jpg
:http://grass.osgeo.org/grass61/screenshots/images/srtmV2_trento_small.jpg
* [http://grass.itc.it/grass61/screenshots/raster.php GRASS 6.1 elevation screenshots]
* [http://grass.osgeo.org/grass61/screenshots/raster.php GRASS 6.1 elevation screenshots]


:[[Image:olympus_mons-medium.jpg]]
:[[Image:olympus_mons-medium.jpg]]
Line 27: Line 27:
== Raster 3D Volumes (voxels) ==
== Raster 3D Volumes (voxels) ==


Support for 3D rasters (voxels) is relatively new in GRASS and is primarily handled by [http://grass.itc.it/grass63/manuals/html63_user/raster3D.html the r3.* modules].
Support for 3D rasters (voxels) is relatively new in GRASS and is primarily handled by {{cmd|raster3D}} - the r3.* modules.
A 3D raster can be thought of as a stack of 2D raster maps forming a 3D cube of data cells.
A 3D raster can be thought of as a stack of 2D raster maps forming a 3D cube of data cells.


* [http://grass.itc.it/grass63/manuals/html63_user/raster3dintro.html An introduction to 3D raster processing in GRASS GIS]
* {{cmd|raster3dintro}} - An introduction to 3D raster processing in GRASS GIS


The third dimension need not be limited to "z" elevation! It can just as well represent the time dimension in a time series of 2.5D raster surfaces. It is possible to make a '''4D''' visualization using the ''NVIZ'' software's animation panels and movie making facility.
The third dimension need not be limited to "z" elevation! It can just as well represent the time dimension in a time series of 2.5D raster surfaces. It is possible to make a '''4D''' visualization using the ''NVIZ'' software's animation panels and movie making facility.
Line 38: Line 38:
:http://grass.ibiblio.org/grass60/screenshots/images/nviz_isosurf3d_small.jpg
:http://grass.ibiblio.org/grass60/screenshots/images/nviz_isosurf3d_small.jpg


* NVIZ [http://grass.itc.it/grass60/screenshots/images/nviz_isosurf3d.jpg Precipitation isosurfaces above Slovakia]
* NVIZ [http://grass.osgeo.org/grass60/screenshots/images/nviz_isosurf3d.jpg Precipitation isosurfaces above Slovakia]


-----
-----
Line 48: Line 48:
-----
-----


http://grass.ibiblio.org/grass63/manuals/html63_user/r.to.rast3.png
http://grass.osgeo.org/grass64/manuals/html64_user/r.to.rast3.png
* [http://grass.ibiblio.org/grass63/manuals/html63_user/r.to.rast3.html r.to.rast3]
* {{cmd|r.to.rast3}}


-----
-----


http://grass.ibiblio.org/grass63/manuals/html63_user/r3.to.rast.png
http://grass.osgeo.org/grass64/manuals/html64_user/r3.to.rast.png
* [http://grass.ibiblio.org/grass63/manuals/html63_user/r3.to.rast.html r3.to.rast]
* {{cmd|r3.to.rast}}


-----
-----


http://grass.ibiblio.org/grass63/manuals/html63_user/r.to.rast3elev.png
http://grass.osgeo.org/grass64/manuals/html64_user/r.to.rast3elev.png
* [http://grass.ibiblio.org/grass63/manuals/html63_user/r.to.rast3elev.html r.to.rast3elev]
* {{cmd|r.to.rast3elev}}


-----
-----


http://grass.ibiblio.org/grass63/manuals/html63_user/r3.cross.rast.png
http://grass.osgeo.org/grass64/manuals/html64_user/r3.cross.rast.png
* [http://grass.ibiblio.org/grass63/manuals/html63_user/r3.cross.rast.html r3.cross.rast]
* {{cmd|r3.cross.rast}}


-----
-----


==== Region settings ====
==== Region settings ====
Region settings are handled by the [http://grass.itc.it/grass63/manuals/html63_user/g.region.html g.region] module.
Region settings are handled by the {{cmd|g.region}} module.
Special 3D raster controls for ''g.region'' include:
Special 3D raster controls for ''g.region'' include:
  -3 flag:  Prints 3D settings
  -3 flag:  Prints 3D settings
Line 81: Line 81:
==== Tips ====
==== Tips ====


* From the mailing list: [http://grass.itc.it/pipermail/grassuser/2006-April/033557.html]
* From the mailing list: [http://grass.osgeo.org/pipermail/grassuser/2006-April/033557.html]


==== Examples ====
==== Examples ====
Line 88: Line 88:




* Custom volume creation. Here is a small ''[http://www.gnu.org/software/octave/ Octave]'' (''Matlab'') script to create a text file suitable for loading as a 3D raster with [http://grass.ibiblio.org/grass63/manuals/html63_user/r3.in.ascii.html r3.in.ascii]. Here is the file that this script creates: [http://bambi.otago.ac.nz/hamish/grass/vox_data50.txt.gz vox_data50.txt.gz]
* Custom volume creation. Here is a small ''[http://www.gnu.org/software/octave/ Octave]'' (''Matlab'') script to create a text file suitable for loading as a 3D raster with {{cmd|r3.in.ascii}}. Here is the file that this script creates: [http://bambi.otago.ac.nz/hamish/grass/vox_data50.txt.gz vox_data50.txt.gz]


  % f(x,y,z) = x + (y^2 /2) + z^2
  % f(x,y,z) = x + (y^2 /2) + z^2
Line 143: Line 143:
In the "typical" case, "z" data is stored as a non-spatial attribute in a vector point map. In GRASS 6 it is possible to create 3D vector files, i.e. points exist in 3D space.
In the "typical" case, "z" data is stored as a non-spatial attribute in a vector point map. In GRASS 6 it is possible to create 3D vector files, i.e. points exist in 3D space.


* [http://grass.itc.it/grass63/manuals/html63_user/vectorintro.html An introduction to vector processing in GRASS GIS]
* {{cmd|vectorintro}} - An introduction to vector processing in GRASS GIS


==== Import ====
==== Import ====


* Import x,y,z,... data as 3D with the [http://grass.itc.it/grass63/manuals/html63_user/v.in.ascii v.in.ascii] "-z" flag and "z=" column parameter:
* Import x,y,z,... data as 3D with the {{cmd|v.in.ascii}} "-z" flag and "z=" column parameter:
  v.in.ascii -z format=point cat=1 x=2 y=3 z=4
  v.in.ascii -z format=point cat=1 x=2 y=3 z=4


* You can convert a 2D vector into a 3D vector with [http://grass.ibiblio.org/grass63/manuals/html63_user/v.extrude.html v.extrude] (take elevation values from vector attribute column) or [http://grass.ibiblio.org/grass63/manuals/html63_user/v.drape.html v.drape] (interpolate elevation values from a raster DEM map).
* You can convert a 2D vector into a 3D vector with {{cmd|v.extrude}} (take elevation values from vector attribute column) or {{cmd|v.drape}} (interpolate elevation values from a raster DEM map).


* It may be more convenient to import massive datasets (millions and millions of points) with [http://grass.itc.it/grass63/manuals/html63_user/r.in.xyz.html r.in.xyz] to create a 2.5D raster map.
* It may be more convenient to import massive datasets (millions and millions of points) with {{cmd|r.in.xyz}} to create a 2.5D raster map.




Line 186: Line 186:
** ''volume'': An enclosed 3D space. The 3D equivalent to GRASS's ''area'' vector feature, meaning an alias to a "face(s)+kernel" set. <!-- HB: this is just a wild guess, I'm really not sure --> (''some infrastructure and place-holders exist, but not much in the way of practical applications has been coded yet'')
** ''volume'': An enclosed 3D space. The 3D equivalent to GRASS's ''area'' vector feature, meaning an alias to a "face(s)+kernel" set. <!-- HB: this is just a wild guess, I'm really not sure --> (''some infrastructure and place-holders exist, but not much in the way of practical applications has been coded yet'')


* [http://grass.itc.it/grass63/manuals/html63_user/vectorintro.html An introduction to vector processing in GRASS GIS]
* {{cmd|vectorintro.html An introduction to vector processing in GRASS GIS]


* The [http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii GRASS ascii format specification]
* The [http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii GRASS ascii format specification]
Line 192: Line 192:
* The ''v.in.ascii'' '''-z''' flag must be used to create a 3D file
* The ''v.in.ascii'' '''-z''' flag must be used to create a 3D file


* The [http://grass.itc.it/grass63/manuals/html63_user/v.in.dxf.html v.in.dxf] or ''v.in.dwg'' modules can import 3D vector surfaces. DXF files are usually imported without georeference. To move into the geo-space of the rest of your data they must be projected with ''v.proj'' or translated with ''v.transform''. If working with them alone, it is recommended to use a simple XY location.
* The {{cmd|v.in.dxf.html v.in.dxf] or ''v.in.dwg'' modules can import 3D vector surfaces. DXF files are usually imported without georeference. To move into the geo-space of the rest of your data they must be projected with ''v.proj'' or translated with ''v.transform''. If working with them alone, it is recommended to use a simple XY location.


* Visualization with NVIZ: must be placed on a raster surface or constant surface. It may be useful to set the transparency attribute of the raster surface to something unobtrusive.
* Visualization with NVIZ: must be placed on a raster surface or constant surface. It may be useful to set the transparency attribute of the raster surface to something unobtrusive.
Line 207: Line 207:


==== Screenshots ====
==== Screenshots ====
* [http://grass.itc.it/grass61/screenshots/vector.php GRASS 6 screenshots]
* [http://grass.osgeo.org/grass61/screenshots/vector.php GRASS 6 screenshots]
:http://grass.itc.it/grass61/screenshots/images/object_nviz_from_dxf_mesh_small.jpg
:http://grass.osgeo.org/grass61/screenshots/images/object_nviz_from_dxf_mesh_small.jpg
* ''3D DXF Mesh object, created in [http://www.blender.org Blender] and imported into GRASS (screenshot: A. Bezzi, M. Neteler)''
* ''3D DXF Mesh object, created in [http://www.blender.org Blender] and imported into GRASS (screenshot: A. Bezzi, M. Neteler)''


:http://grass.itc.it/grass61/screenshots/images/trento3d_small.jpg
:http://grass.osgeo.org/grass61/screenshots/images/trento3d_small.jpg
* '' GRASS: building footprints extruded to 3D blocks (screenshot: M. Neteler)
* '' GRASS: building footprints extruded to 3D blocks (screenshot: M. Neteler)
:(data courtesy City of Trento, Italy - see "Mostra Strumenti Dati" for geodata download)''
:(data courtesy City of Trento, Italy - see "Mostra Strumenti Dati" for geodata download)''
Line 262: Line 262:
== Visualization Tools ==
== Visualization Tools ==


* [http://grass.itc.it/grass63/manuals/html63_user/nviz/index.html NVIZ]: GRASS's own visualization suite
* {{cmd|nviz}}: GRASS's own visualization suite
** [http://grass.itc.it/grass60/screenshots/viz.php Screenshots]
** [http://grass.osgeo.org/screenshots/viz.php Screenshots]


* output to VTK & Paraview ([http://grass.itc.it/grass63/manuals/html63_user/r.out.vtk.html r.out.vtk], [http://grass.itc.it/grass63/manuals/html63_user/r3.out.vtk.html r3.out.vtk], [http://grass.itc.it/grass63/manuals/html63_user/v.out.vtk.html v.out.vtk])
* output to VTK & Paraview ({{cmd|r.out.vtk}}, {{cmd|r3.out.vtk}}, {{cmd|v.out.vtk}})
** [http://www-pool.math.tu-berlin.de/~soeren/grass/modules/screenshots/ Screenshots] (seek Para* there)
** [http://www-pool.math.tu-berlin.de/~soeren/grass/modules/screenshots/ Screenshots] (seek Para* there)


* output to POVray ([http://grass.itc.it/grass63/manuals/html63_user/r.out.pov.html r.out.pov], [http://grass.itc.it/grass63/manuals/html63_user/v.out.pov.html v.out.pov])
* output to POVray ({{cmd|r.out.pov}}, {{cmd|v.out.pov}})
** [http://mpa.itc.it/markus/povray/ Screenshots]
** [http://mpa.itc.it/markus/povray/ Screenshots]


* output to Vis5D ([http://grass.itc.it/grass63/manuals/html63_user/r3.out.v5d.html r3.out.v5d])
* output to Vis5D ({{cmd|r3.out.v5d}})


* output to VRML (3D virtual reality) ([http://grass.itc.it/grass63/manuals/html63_user/r.out.vrml.html r.out.vrml])
* output to VRML (3D virtual reality) ({{cmd|r.out.vrml}})


* output to KML (Google Earth) ([http://grass.itc.it/grass63/manuals/html63_user/v.out.ogr.html v.out.ogr])
* output to KML (Google Earth) ({{cmd|v.out.ogr}})


* output to DXF (Blender, AutoCAD, ...) ([http://grass.itc.it/grass63/manuals/html63_user/v.out.dxf.html v.out.dxf])
* output to DXF (Blender, AutoCAD, ...) ({{cmd|v.out.dxf}})


[[Category:Documentation]]
[[Category:Documentation]]

Revision as of 09:41, 6 April 2009

Raster 2.5D Surfaces

This is the "typical" case, and most raster (GRASS r.* modules) work in this mode. The GIS layer is defined by north,south,east,west and the raster map's cell values represent the elevation.

  • rasterintro: An introduction to raster processing in GRASS GIS

Snippet from the Wikipedia definition for 2.5D: "The idea is that the program's canvas represents a normal 2D painting surface, but that the data structure that holds the pixel information is also able to store information regarding z-index (depth) as well as other information such as material settings, specularity, etc. With this data it is thus possible to simulate lighting, shadows, and so on."

Horizontal (2D) region settings are handled by the g.region module. The third dimension is unbound.

2.5D rasters may be visualized in 3D with GRASS's nviz program, or as a shaded relief in 2D space with the r.shaded.relief module.

Screenshots

http://grass.osgeo.org/grass61/screenshots/images/srtmV2_trento_small.jpg

Example

(spearfish dataset)

g.region rast=elevation.10m
nviz elev=elevation.10m

Raster 3D Volumes (voxels)

Support for 3D rasters (voxels) is relatively new in GRASS and is primarily handled by raster3D - the r3.* modules. A 3D raster can be thought of as a stack of 2D raster maps forming a 3D cube of data cells.

  • raster3dintro - An introduction to 3D raster processing in GRASS GIS

The third dimension need not be limited to "z" elevation! It can just as well represent the time dimension in a time series of 2.5D raster surfaces. It is possible to make a 4D visualization using the NVIZ software's animation panels and movie making facility.

Screenshots

http://grass.ibiblio.org/grass60/screenshots/images/nviz_isosurf3d_small.jpg

http://skagit.meas.ncsu.edu/~helena/gmslab/viz/img/chal3d_i.gif http://skagit.meas.ncsu.edu/~helena/gmslab/viz/img/chal4d_i.gif

http://grass.osgeo.org/grass64/manuals/html64_user/r.to.rast3.png


http://grass.osgeo.org/grass64/manuals/html64_user/r3.to.rast.png


http://grass.osgeo.org/grass64/manuals/html64_user/r.to.rast3elev.png


http://grass.osgeo.org/grass64/manuals/html64_user/r3.cross.rast.png


Region settings

Region settings are handled by the g.region module. Special 3D raster controls for g.region include:

-3 flag:  Prints 3D settings
 rast3d   Set region to match this 3D raster map (both 2D and 3D values)
      t   Value for the top edge
      b   Value for the bottom edge
   res3   3D grid resolution (north-south, east-west and top-bottom)
  tbres   Top-bottom grid resolution 3D

Tips

  • From the mailing list: [1]

Examples


  • Custom volume creation. Here is a small Octave (Matlab) script to create a text file suitable for loading as a 3D raster with r3.in.ascii. Here is the file that this script creates: vox_data50.txt.gz
% f(x,y,z) = x + (y^2 /2) + z^2
x= y= z= 50;

cd ~/grass/
fp = fopen('vox_data50.txt', 'wt')

fprintf(fp, 'north: %d\n', y);
fprintf(fp, 'south: 0\n');
fprintf(fp, 'east: %d\n', x);
fprintf(fp, 'west: 0\n');
fprintf(fp, 'top: %d\n', z);
fprintf(fp, 'bottom: 0\n');
fprintf(fp, 'rows: %d\n', y);
fprintf(fp, 'cols: %d\n', x);
fprintf(fp, 'levels: %d\n', z);

for dep = 1:z
  for row = 1:y
    for col = 1:x
       fprintf(fp, '%.4f', col + (row^2 /2) + dep^2 );
       if(col < 50)
          fprintf(fp, ' ');
       end
    end
    fprintf(fp, '\n');
  end
  disp(['dep ' num2str(dep)])
  fflush(stdout);
end
fclose(fp)

Load the data with:

r3.in.ascii in=vox_data50.txt out=vox50

display isosurfaces with:

g.region rast3d=vox50
nviz -q
Panel->Raster volumes
[New] vox50
Isosurface [Add] [New Constant] 500 [Accept]  
 (repeat for 1000,2000,3000)
Change main view height to 125.00 (manual entry)

extract a slice to a 2D raster map with:

g.region t=26.0 b=25.0
r3.to.rast in=vox50 out=vox50x

Vector 3D point data

Historical note: known as "site data" in GRASS GIS 5

In the "typical" case, "z" data is stored as a non-spatial attribute in a vector point map. In GRASS 6 it is possible to create 3D vector files, i.e. points exist in 3D space.

  • vectorintro - An introduction to vector processing in GRASS GIS

Import

  • Import x,y,z,... data as 3D with the v.in.ascii "-z" flag and "z=" column parameter:
v.in.ascii -z format=point cat=1 x=2 y=3 z=4
  • You can convert a 2D vector into a 3D vector with v.extrude (take elevation values from vector attribute column) or v.drape (interpolate elevation values from a raster DEM map).
  • It may be more convenient to import massive datasets (millions and millions of points) with r.in.xyz to create a 2.5D raster map.


Conversion to 3D raster volume

  • Use the v.vol.rst module to interpolate 3D vector points into a 3D raster volume.

Screenshot

3D points defining the hull of a ship, visualized using NVIZ

Example

TODO: import star guide and display using NVIZ, using magnitude column in database table for dynamic sizing. Requires a "Free" dataset, if you have any leads, please add links to this wiki page. Thanks.

Vector 3D lines

The GRASS vector engine is fully 3D aware, so 3D lines such as highways which cross at a bridge, but do not touch, can be modelled.

  • 3D line objects can be displayed with NVIZ
(place above a 2D raster isosurface)

Vector 3D polygons

In the "typical" case, "z" data is stored as a non-spatial attribute in a vector point map. In GRASS 6 it is possible to create 3D vector files, i.e. lines and polygons exist in 3D space. The topological nature of GRASS 6's vector engine means that roads can cross via a bridge without topologically meeting.

  • 3D feature types
    • face: The 3D equivalent of a boundary. These combine to form a volume surface (e.g. a teapot)
    • kernel: The 3D equivalent of a centroid (infrastructure for kernels is in place, but they are currently mostly unused)
    • volume: An enclosed 3D space. The 3D equivalent to GRASS's area vector feature, meaning an alias to a "face(s)+kernel" set. (some infrastructure and place-holders exist, but not much in the way of practical applications has been coded yet)
  • {{cmd|vectorintro.html An introduction to vector processing in GRASS GIS]
  • The v.in.ascii -z flag must be used to create a 3D file
  • The {{cmd|v.in.dxf.html v.in.dxf] or v.in.dwg modules can import 3D vector surfaces. DXF files are usually imported without georeference. To move into the geo-space of the rest of your data they must be projected with v.proj or translated with v.transform. If working with them alone, it is recommended to use a simple XY location.
  • Visualization with NVIZ: must be placed on a raster surface or constant surface. It may be useful to set the transparency attribute of the raster surface to something unobtrusive.

Getting data and data conversion

There are many free 3D mesh files available for research purposes from INRIA.fr's GAMMA project. These can be converted from e.g. 3D Studio (.3ds) format into DXF files with a converter program like wcvt2pov.exe (runs well in Linux under wine). Then use v.in.dxf. Also Blender does a nice job for exporting to 3D DXF.

wcvt2pov.exe supported file formats

  • load: AOFF (*.geo), AutoCAD DXF (*.dxf), 3D Studio (*.3ds), Neutral File Format (*.nff), RAW (*.raw), TPOLY (*.tpo), True Type Font (*.ttf), Wavefront (*.obj), World Toolkit (*.nff)
  • save: AutoCAD DXF (*.dxf), 3D Studio (*.asc), Neutral File Format (*.nff), Povray V2.2 (*.pov), Povray V2.2 Include (*.inc), RAW (*.raw), TPOLY (*.tpo), True Space (*.cob), VRML V1.0 (*.wrl), Wavefront (*.obj), World Toolkit (*.nff)

Screenshots

http://grass.osgeo.org/grass61/screenshots/images/object_nviz_from_dxf_mesh_small.jpg
  • 3D DXF Mesh object, created in Blender and imported into GRASS (screenshot: A. Bezzi, M. Neteler)
http://grass.osgeo.org/grass61/screenshots/images/trento3d_small.jpg
  • GRASS: building footprints extruded to 3D blocks (screenshot: M. Neteler)
(data courtesy City of Trento, Italy - see "Mostra Strumenti Dati" for geodata download)
  • Watertower imported with v.in.dwg (or use v.in.dxf) displayed over a 2.5D raster surface with color orthophoto raster providing ground coloration.

Example

pyramid: the following is an example of 3D vector surfaces in GRASS's standard ascii format. load with v.in.ascii.

# 3D Pyramid in GRASS:  (kernel type still unused in GRASS 6)
#  v.in.ascii in=pyramid.vasc out=pyramid_3d format=standard -nz
#  g.region n=150 s=-50 w=-50 e=150 res=10
#  r.mapcalc one=1
#  nviz elev=one vect=pyramid_3d
#
#  tip: in nviz try setting the raster surface transparency to 50%
#
F 5
 0 0 10
 0 100 10
 100 100 10
 100 0 10
 0 0 10
F 4
 0 0 10
 50 50 80
 100 0 10
 0 0 10
F 4
 0 100 10
 50 50 80
 0 0 10
 0 100 10
F 4
 100 100 10
 50 50 80
 0 100 10
 100 100 10
F 4
 100 0 10
 50 50 80
 100 100 10
 100 0 10
K 1 1
 40 50 40
 1 1

Visualization Tools

  • output to DXF (Blender, AutoCAD, ...) (v.out.dxf)