<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-2">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>ODP: [GRASS-user] vrml import to grass</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>hi<BR>
<BR>
The wrml i have is 3d model of cave, i created ascii file and i imported it in to grass (but only points),<BR>
but i found a way to import this in to grass. First, import to blender and export to .dxf and then import .dxf in to grass (v.in.dxf).<BR>
best<BR>
mt<BR>
<BR>
<BR>
Maciej Tomaszczyk<BR>
Polish Geological Institute<BR>
Geological Mapping Department<BR>
<A HREF="http://www.pgi.gov.pl">http://www.pgi.gov.pl</A><BR>
<A HREF="http://www.opengeology.pl">http://www.opengeology.pl</A><BR>
<BR>
<BR>
<BR>
-----Wiadomość oryginalna-----<BR>
Od: Glynn Clements [<A HREF="mailto:glynn@gclements.plus.com">mailto:glynn@gclements.plus.com</A>]<BR>
Wysłano: Śr 2008-03-19 05:37<BR>
Do: Maciej Tomaszczyk<BR>
DW: grass-user@lists.osgeo.org<BR>
Temat: Re: [GRASS-user] vrml import to grass<BR>
<BR>
<BR>
Maciej Tomaszczyk wrote:<BR>
<BR>
> i am wonder if is a way to import wrml file in to the GRASS.<BR>
> There is v.out.vrml but i cant find any command to import this type of file.<BR>
> best<BR>
<BR>
VRML is a general purpose 3D modelling format. The only node type<BR>
which has any real relation to GIS is the ElevationGrid type. This is<BR>
what v.out.vrml generates.<BR>
<BR>
If you have a VRML file which is essentially a DEM which has been<BR>
converted to an ElevationGrid, I suggest extracting the actual<BR>
coordinate data using a text editor (or sed) then importing it with<BR>
r.in.ascii.<BR>
<BR>
A VRML importer would require a fair amount of effort (it would need a<BR>
full VRML parser just to extract ElevationGrid nodes), and I'm<BR>
doubtful of its utility, given that any suitable VRML files would<BR>
almost invariably have been generated from some other format, and the<BR>
original data would probably be far more amenable to importation (i.e.<BR>
GRASS probably already supports the format, and may be able to obtain<BR>
georeferencing information from it).<BR>
<BR>
--<BR>
Glynn Clements <glynn@gclements.plus.com><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>