On the manual page for r.to.rast3, under Notes, it says “If fewer 2D raster maps are provided than depths, the last give 2D map is used to fill up the RASTER3D slices to the top”. How do you define the depths?
Perhaps related, in Example 2 it says that it “shows how to convert 3 maps into 3d map with 6 layers”. Why 6 layers, what determines that 6 layers are created?
Hi,
you can specify the 3D region with g.region, which includes the top,
bottom and res3/tbres settings. These settings define the number of
depths. Its the same principle as for row and columns.
r3.info will show you the number of depths for a voxel map.
Best regards
Soeren
2015-03-17 9:45 GMT+01:00 Paulo van Breugel <p.vanbreugel@gmail.com>:
On the manual page for r.to.rast3, under Notes, it says "If fewer 2D raster
maps are provided than depths, the last give 2D map is used to fill up the
RASTER3D slices to the top". How do you define the depths?Perhaps related, in Example 2 it says that it "shows how to convert 3 maps
into 3d map with 6 layers". Why 6 layers, what determines that 6 layers are
created?_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Thanks, clear now 
Op di 17 mrt. 2015 09:49 schreef Sören Gebbert <soerengebbert@googlemail.com>:
Hi,
you can specify the 3D region with g.region, which includes the top,
bottom and res3/tbres settings. These settings define the number of
depths. Its the same principle as for row and columns.r3.info will show you the number of depths for a voxel map.
Best regards
Soeren2015-03-17 9:45 GMT+01:00 Paulo van Breugel <p.vanbreugel@gmail.com>:
On the manual page for r.to.rast3, under Notes, it says “If fewer 2D raster
maps are provided than depths, the last give 2D map is used to fill up the
RASTER3D slices to the top”. How do you define the depths?Perhaps related, in Example 2 it says that it “shows how to convert 3 maps
into 3d map with 6 layers”. Why 6 layers, what determines that 6 layers are
created?
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Tue, Mar 17, 2015 at 10:09 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
Thanks, clear now
Please suggest manual improvements...
thanks
Markus
On Tue, Mar 17, 2015 at 2:40 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Tue, Mar 17, 2015 at 10:09 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
> Thanks, clear nowPlease suggest manual improvements...
thanks
Markus
I have no experience using the 3D rasters, so I will keep it to some more
generic suggestions:
Perhaps a suggestion would be to start both examples with a line in which
the region in set, e.g., g.region b=0 t=600 tbres=100 res3=100
In the description, perhaps adding more explicitly that one needs to take
care to set the 3d region settings, including number or layers and depth of
layer, with g.region.
On Thu, Mar 19, 2015 at 10:15 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
On Tue, Mar 17, 2015 at 2:40 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Tue, Mar 17, 2015 at 10:09 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
> Thanks, clear nowPlease suggest manual improvements...
thanks
MarkusI have no experience using the 3D rasters, so I will keep it to some more
generic suggestions:Perhaps a suggestion would be to start both examples with a line in which
the region in set, e.g., g.region b=0 t=600 tbres=100 res3=100In the description, perhaps adding more explicitly that one needs to take
care to set the 3d region settings, including number or layers and depth of
layer, with g.region.
I have made an attempt in
https://trac.osgeo.org/grass/changeset/64889
Markus