[GRASS-user] v.vol.rst - DMIN and Segment Size

Hi,

I am trying to use V.VOL.RST to interpolate particle size for soil samples. i obtain the error message to increase DMin. unfortunately i have a data point every meter vertically and a total of 190K. if grass is asking to increase DMIN, which i have increased to 30 m to try to see if this was the pb, can I resolve this by reducing the Segment size?

COMMAND OUTPUT

(Thu Nov 08 06:17:32 2018) Command finished (10 sec)
(Thu Nov 08 06:20:40 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50 npmax=200 dmin=30 elevation=Geotech3DNov8
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Thu Nov 08 06:20:51 2018) Command finished (10 sec)

METADATA

Thu Nov 08 06:11:32 2018) Command finished (0 sec)
(Thu Nov 08 06:19:17 2018)
v.info map=geotechNov8@Toronto
±---------------------------------------------------------------------------+
| Name: geotechNov8 |
| Mapset: Toronto |
| Location: Toronto |
| Database: C:\Users\Francois Chartier\Documents\grassdata |
| Title: |
| Map scale: 1:1 |
| Name of creator: Francois Chartier |
| Organization: |
| Source date: Thu Nov 08 06:06:56 2018 |

Timestamp (first layer): none
Map format: native
----------------------------------------------------------------------------
Type of map: vector (level: 2)
Number of points: 188692 Number of centroids: 0
Number of lines: 0 Number of boundaries: 0
Number of areas: 0 Number of islands: 0
Number of faces: 0 Number of kernels: 0
Number of volumes: 0 Number of holes: 0
Map is 3D: Yes
Number of dblinks: 1
Projection: UTM (zone 17)
N: 4870782 S: 4825713
E: 651697 W: 609201
B: 0 T: 352
Digitization threshold: 0
Comment:
±---------------------------------------------------------------------------+
(Thu Nov 08 06:19:18 2018) Command finished (0 sec)

does anybody know how to resolve this?

On Thu, Nov 8, 2018, 06:23 Francois Chartier <fra.chartier@gmail.com wrote:

Hi,

I am trying to use V.VOL.RST to interpolate particle size for soil samples. i obtain the error message to increase DMin. unfortunately i have a data point every meter vertically and a total of 190K. if grass is asking to increase DMIN, which i have increased to 30 m to try to see if this was the pb, can I resolve this by reducing the Segment size?

COMMAND OUTPUT

(Thu Nov 08 06:17:32 2018) Command finished (10 sec)
(Thu Nov 08 06:20:40 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50 npmax=200 dmin=30 elevation=Geotech3DNov8
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Thu Nov 08 06:20:51 2018) Command finished (10 sec)

METADATA

Thu Nov 08 06:11:32 2018) Command finished (0 sec)
(Thu Nov 08 06:19:17 2018)
v.info map=geotechNov8@Toronto
±---------------------------------------------------------------------------+
| Name: geotechNov8 |
| Mapset: Toronto |
| Location: Toronto |
| Database: C:\Users\Francois Chartier\Documents\grassdata |
| Title: |
| Map scale: 1:1 |
| Name of creator: Francois Chartier |
| Organization: |
| Source date: Thu Nov 08 06:06:56 2018 |

Timestamp (first layer): none
Map format: native
----------------------------------------------------------------------------
Type of map: vector (level: 2)
Number of points: 188692 Number of centroids: 0
Number of lines: 0 Number of boundaries: 0
Number of areas: 0 Number of islands: 0
Number of faces: 0 Number of kernels: 0
Number of volumes: 0 Number of holes: 0
Map is 3D: Yes
Number of dblinks: 1
Projection: UTM (zone 17)
N: 4870782 S: 4825713
E: 651697 W: 609201
B: 0 T: 352
Digitization threshold: 0
Comment:
±---------------------------------------------------------------------------+
(Thu Nov 08 06:19:18 2018) Command finished (0 sec)

Hi,

v.vol.rst starts working when npmin is 100 m or more. I dont believe that this algorythm only works with data points spaced by 100 m that does not make sense. is there a max total number for a dataset? is it because i have too few rows and columns?
see metadata below. i also showed a lower dmin of 0.9. g.region is printed at the end of the email

±---------------------------------------------------------------------------+
|

|----------------------------------------------------------------------------|
| |
| Type of Map: raster_3d Number of Categories: 0 |
| Data Type: FCELL |
| Rows: 90 |
| Columns: 85 |
| Depths: 2 |
| Total Cells: 15300 |
| Total size: 48229 Bytes |
| Number of tiles: 4 |
| Mean tile size: 12057 Bytes |
| Tile size in memory: 15480 Bytes |
| Number of tiles in x, y and z: 2, 2, 1 |
| Dimension of a tile in x, y, z: 43, 45, 2 |
| |
| Projection: UTM (zone 17) |
| N: 4870782 S: 4825713 Res: 500.76666667 |
| E: 651697 W: 609201 Res: 499.95294118 |
| T: 352 B: 0 Res: 176 |
| Range of data: min = -1.17721057 max = 89.22615051 |
| |
| Data Source: |
| |
| |
| |
| Data Description: |
| generated by v.vol.rst |
| |
| Comments: |
| v.vol.rst --overwrite input=“geotechNov8@Toronto” wcolumn=“dbl_2” te\ |
| nsion=40. smooth=0.1 segmax=50 npmin=200 npmax=700 dmin=100 wscale=1\ |
| .0 zscale=1.0 elevation=“geotechnov8” |
| |
±---------------------------------------------------------------------------+
(Tue Nov 13 19:18:12 2018) Command finished (0 sec)

i have also tried with low dmin of 0.9 m:

(Tue Nov 13 19:22:49 2018)
v.vol.rst --overwrite input=geotechNov8@Toronto wcolumn=dbl_2 npmin=60 npmax=100 dmin=0.9 elevation=geotechnov13
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Tue Nov 13 19:23:00 2018) Command finished (10 sec)

METADATA of Vector points

Thu Nov 08 06:06:56 2018 |

Timestamp (first layer): none
Map format: native
----------------------------------------------------------------------------
Type of map: vector (level: 2)
Number of points: 188692 Number of centroids: 0
Number of lines: 0 Number of boundaries: 0
Number of areas: 0 Number of islands: 0
Number of faces: 0 Number of kernels: 0
Number of volumes: 0 Number of holes: 0
Map is 3D: Yes
Number of dblinks: 1
Projection: UTM (zone 17)
N: 4870782 S: 4825713
E: 651697 W: 609201
B: 0 T: 352
Digitization threshold: 0
Comment:
±---------------------------------------------------------------------------+
(Tue Nov 13 19:25:30 2018) Command finished (0 sec)

g.region - p

projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
nsres: 10
ewres: 10
rows: 3630
cols: 4250
cells: 15427500

Le ven. 9 nov. 2018 à 07:16, Francois Chartier <fra.chartier@gmail.com> a écrit :

does anybody know how to resolve this?

On Thu, Nov 8, 2018, 06:23 Francois Chartier <fra.chartier@gmail.com wrote:

Hi,

I am trying to use V.VOL.RST to interpolate particle size for soil samples. i obtain the error message to increase DMin. unfortunately i have a data point every meter vertically and a total of 190K. if grass is asking to increase DMIN, which i have increased to 30 m to try to see if this was the pb, can I resolve this by reducing the Segment size?

COMMAND OUTPUT

(Thu Nov 08 06:17:32 2018) Command finished (10 sec)
(Thu Nov 08 06:20:40 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50 npmax=200 dmin=30 elevation=Geotech3DNov8
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Thu Nov 08 06:20:51 2018) Command finished (10 sec)

METADATA

Thu Nov 08 06:11:32 2018) Command finished (0 sec)
(Thu Nov 08 06:19:17 2018)
v.info map=geotechNov8@Toronto
±---------------------------------------------------------------------------+
| Name: geotechNov8 |
| Mapset: Toronto |
| Location: Toronto |
| Database: C:\Users\Francois Chartier\Documents\grassdata |
| Title: |
| Map scale: 1:1 |
| Name of creator: Francois Chartier |
| Organization: |
| Source date: Thu Nov 08 06:06:56 2018 |

Timestamp (first layer): none
Map format: native
----------------------------------------------------------------------------
Type of map: vector (level: 2)
Number of points: 188692 Number of centroids: 0
Number of lines: 0 Number of boundaries: 0
Number of areas: 0 Number of islands: 0
Number of faces: 0 Number of kernels: 0
Number of volumes: 0 Number of holes: 0
Map is 3D: Yes
Number of dblinks: 1
Projection: UTM (zone 17)
N: 4870782 S: 4825713
E: 651697 W: 609201
B: 0 T: 352
Digitization threshold: 0
Comment:
±---------------------------------------------------------------------------+
(Thu Nov 08 06:19:18 2018) Command finished (0 sec)

On 14/11/18 01:28, Francois Chartier wrote:

Hi,

v.vol.rst starts working when npmin is 100 m or more. I dont believe that this algorythm only works with data points spaced by 100 m that does not make sense. is there a max total number for a dataset? is it because i have too few rows and columns?
see metadata below. i also showed a lower dmin of 0.9. g.region is printed at the end of the email

Your g.region output does not correspond to the region that was set when you ran v.vol.rst as the map created has a resolution of 500 in x and y direction, but your region says 10.

Could you provide the output of g.region -p3 to also get the 3D settings ?

I don't have an exact idea, but the map you created has a resolution of 500 x 500 x 176, so maybe if you have a point per meter this just means that the number of points you have per target pixel is much too high.

Maybe you need to think about the appropriate 3D region first and make sure to set that before running v.vol.rst ?

Moritz

+----------------------------------------------------------------------------+
|
|----------------------------------------------------------------------------|
| |
| Type of Map: raster_3d Number of Categories: 0 |
| Data Type: FCELL |
| Rows: 90 |
| Columns: 85 |
| Depths: 2 |
| Total Cells: 15300 |
| Total size: 48229 Bytes |
| Number of tiles: 4 |
| Mean tile size: 12057 Bytes |
| Tile size in memory: 15480 Bytes |
| Number of tiles in x, y and z: 2, 2, 1 |
| Dimension of a tile in x, y, z: 43, 45, 2 |
| |
| Projection: UTM (zone 17) |
| N: 4870782 S: 4825713 Res: 500.76666667 |
| E: 651697 W: 609201 Res: 499.95294118 |
| T: 352 B: 0 Res: 176 |
| Range of data: min = -1.17721057 max = 89.22615051 |
| |
| Data Source: |
| |
| |
| |
| Data Description: |
| generated by v.vol.rst |
| |
| Comments: |
| v.vol.rst --overwrite input="geotechNov8@Toronto" wcolumn="dbl_2" te\ |
| nsion=40. smooth=0.1 segmax=50 npmin=200 npmax=700 dmin=100 wscale=1\ |
| .0 zscale=1.0 elevation="geotechnov8" |
| |
+----------------------------------------------------------------------------+
(Tue Nov 13 19:18:12 2018) Command finished (0 sec)

*i have also tried with low dmin of 0.9 m:*

(Tue Nov 13 19:22:49 2018)
v.vol.rst --overwrite input=geotechNov8@Toronto wcolumn=dbl_2 npmin=60 npmax=100 dmin=0.9 elevation=geotechnov13
188692 records selected from table
WARNING: Some points outside of region -- will ignore...
ERROR: Points are too concentrated -- please increase DMIN
(Tue Nov 13 19:23:00 2018) Command finished (10 sec)

METADATA of Vector points

Thu Nov 08 06:06:56 2018 |
| Timestamp (first layer): none |
|----------------------------------------------------------------------------|
| Map format: native |
|----------------------------------------------------------------------------|
| Type of map: vector (level: 2) |
| |
| Number of points: 188692 Number of centroids: 0 |
| Number of lines: 0 Number of boundaries: 0 |
| Number of areas: 0 Number of islands: 0 |
| Number of faces: 0 Number of kernels: 0 |
| Number of volumes: 0 Number of holes: 0 |
| |
| Map is 3D: Yes |
| Number of dblinks: 1 |
| |
| Projection: UTM (zone 17) |
| |
| N: 4870782 S: 4825713 |
| E: 651697 W: 609201 |
| B: 0 T: 352 |
| |
| Digitization threshold: 0 |
| Comment: |
| |
+----------------------------------------------------------------------------+
(Tue Nov 13 19:25:30 2018) Command finished (0 sec)

g.region - p

projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
nsres: 10
ewres: 10
rows: 3630
cols: 4250
cells: 15427500

Le ven. 9 nov. 2018 à 07:16, Francois Chartier <fra.chartier@gmail.com <mailto:fra.chartier@gmail.com>> a écrit :

    does anybody know how to resolve this?

    On Thu, Nov 8, 2018, 06:23 Francois Chartier <fra.chartier@gmail.com
    <mailto:fra.chartier@gmail.com> wrote:

        Hi,

        I am trying to use V.VOL.RST to interpolate particle size for
        soil samples. i obtain the error message to increase DMin.
        unfortunately i have a data point every meter vertically and a
        total of 190K. if grass is asking to increase DMIN, which i
        have increased to 30 m to try to see if this was the pb, can I
        resolve this by reducing the Segment size?

        * COMMAND OUTPUT*
        (Thu Nov 08 06:17:32 2018) Command finished (10 sec)
        (Thu Nov 08 06:20:40 2018)
        v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50
        npmax=200 dmin=30 elevation=Geotech3DNov8
        188692 records selected from table
        WARNING: Some points outside of region -- will ignore...
        ERROR: Points are too concentrated -- please increase DMIN
        (Thu Nov 08 06:20:51 2018) Command finished (10 sec)

        *METADATA*
        Thu Nov 08 06:11:32 2018) Command finished (0 sec)
        (Thu Nov 08 06:19:17 2018)
        v.info <http://v.info> map=geotechNov8@Toronto
          +----------------------------------------------------------------------------+
          | Name: geotechNov8 |
          | Mapset: Toronto |
          | Location: Toronto |
          | Database: C:\Users\Francois
        Chartier\Documents\grassdata |
          | Title: |
          | Map scale: 1:1 |
          | Name of creator: Francois Chartier |
          | Organization: |
          | Source date: Thu Nov 08 06:06:56 2018 |
          | Timestamp (first layer): none |
          |----------------------------------------------------------------------------|
          | Map format: native |
          |----------------------------------------------------------------------------|
          | Type of map: vector (level: 2) |
          | |
          | Number of points: 188692 Number of
        centroids: 0 |
          | Number of lines: 0 Number of
        boundaries: 0 |
          | Number of areas: 0 Number of
        islands: 0 |
          | Number of faces: 0 Number of
        kernels: 0 |
          | Number of volumes: 0 Number of holes: 0 |
          | |
          | Map is 3D: Yes |
          | Number of dblinks: 1 |
          | |
          | Projection: UTM (zone 17) |
          | |
          | N: 4870782 S: 4825713 |
          | E: 651697 W: 609201 |
          | B: 0 T: 352 |
          | |
          | Digitization threshold: 0 |
          | Comment: |
          | |
          +----------------------------------------------------------------------------+
        (Thu Nov 08 06:19:18 2018) Command finished (0 sec)

N�n�r����)em�h�yhiם�w^���

good point. i created the 3d raster before. see g.region -p3 below.
I will rerun v.vol.rst with the higher 3d g.region resolution, and keep increasing the dmin until it runs.

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

Virus-free. www.avast.com

Le mer. 14 nov. 2018 à 09:38, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 14/11/18 01:28, Francois Chartier wrote:

Hi,

v.vol.rst starts working when npmin is 100 m or more. I dont believe
that this algorythm only works with data points spaced by 100 m that
does not make sense. is there a max total number for a dataset? is it
because i have too few rows and columns?
see metadata below. i also showed a lower dmin of 0.9. g.region is
printed at the end of the email

Your g.region output does not correspond to the region that was set when
you ran v.vol.rst as the map created has a resolution of 500 in x and y
direction, but your region says 10.

Could you provide the output of g.region -p3 to also get the 3D settings ?

I don’t have an exact idea, but the map you created has a resolution of
500 x 500 x 176, so maybe if you have a point per meter this just means
that the number of points you have per target pixel is much too high.

Maybe you need to think about the appropriate 3D region first and make
sure to set that before running v.vol.rst ?

Moritz

±---------------------------------------------------------------------------+
|
|----------------------------------------------------------------------------|
|
|
| Type of Map: raster_3d Number of Categories: 0
|
| Data Type: FCELL
|
| Rows: 90
|
| Columns: 85
|
| Depths: 2
|
| Total Cells: 15300
|
| Total size: 48229 Bytes
|
| Number of tiles: 4
|
| Mean tile size: 12057 Bytes
|
| Tile size in memory: 15480 Bytes
|
| Number of tiles in x, y and z: 2, 2, 1
|
| Dimension of a tile in x, y, z: 43, 45, 2
|
|
|
| Projection: UTM (zone 17)
|
| N: 4870782 S: 4825713 Res: 500.76666667
|
| E: 651697 W: 609201 Res: 499.95294118
|
| T: 352 B: 0 Res: 176
|
| Range of data: min = -1.17721057 max = 89.22615051
|
|
|
| Data Source:
|
|
|
|
|
|
|
| Data Description:
|
| generated by v.vol.rst
|
|
|
| Comments:
|
| v.vol.rst --overwrite input=“geotechNov8@Toronto” wcolumn=“dbl_2”
te\ |
| nsion=40. smooth=0.1 segmax=50 npmin=200 npmax=700 dmin=100
wscale=1\ |
| .0 zscale=1.0 elevation=“geotechnov8”
|
|
|
±---------------------------------------------------------------------------+
(Tue Nov 13 19:18:12 2018) Command finished (0 sec)

i have also tried with low dmin of 0.9 m:

(Tue Nov 13 19:22:49 2018)
v.vol.rst --overwrite input=geotechNov8@Toronto wcolumn=dbl_2 npmin=60
npmax=100 dmin=0.9 elevation=geotechnov13
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Tue Nov 13 19:23:00 2018) Command finished (10 sec)

METADATA of Vector points

Thu Nov 08 06:06:56 2018 |
| Timestamp (first layer): none
|
|----------------------------------------------------------------------------|
| Map format: native
|
|----------------------------------------------------------------------------|
| Type of map: vector (level: 2)
|
|
|
| Number of points: 188692 Number of centroids: 0
|
| Number of lines: 0 Number of boundaries: 0
|
| Number of areas: 0 Number of islands: 0
|
| Number of faces: 0 Number of kernels: 0
|
| Number of volumes: 0 Number of holes: 0
|
|
|
| Map is 3D: Yes
|
| Number of dblinks: 1
|
|
|
| Projection: UTM (zone 17)
|
|
|
| N: 4870782 S: 4825713
|
| E: 651697 W: 609201
|
| B: 0 T: 352
|
|
|
| Digitization threshold: 0
|
| Comment:
|
|
|
±---------------------------------------------------------------------------+
(Tue Nov 13 19:25:30 2018) Command finished (0 sec)

g.region - p

projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
nsres: 10
ewres: 10
rows: 3630
cols: 4250
cells: 15427500

Le ven. 9 nov. 2018 à 07:16, Francois Chartier <fra.chartier@gmail.com
mailto:[fra.chartier@gmail.com](mailto:fra.chartier@gmail.com)> a écrit :

does anybody know how to resolve this?

On Thu, Nov 8, 2018, 06:23 Francois Chartier <fra.chartier@gmail.com
mailto:[fra.chartier@gmail.com](mailto:fra.chartier@gmail.com) wrote:

Hi,

I am trying to use V.VOL.RST to interpolate particle size for
soil samples. i obtain the error message to increase DMin.
unfortunately i have a data point every meter vertically and a
total of 190K. if grass is asking to increase DMIN, which i
have increased to 30 m to try to see if this was the pb, can I
resolve this by reducing the Segment size?

  • COMMAND OUTPUT*
    (Thu Nov 08 06:17:32 2018) Command finished (10 sec)
    (Thu Nov 08 06:20:40 2018)
    v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50
    npmax=200 dmin=30 elevation=Geotech3DNov8
    188692 records selected from table
    WARNING: Some points outside of region – will ignore…
    ERROR: Points are too concentrated – please increase DMIN
    (Thu Nov 08 06:20:51 2018) Command finished (10 sec)

METADATA
Thu Nov 08 06:11:32 2018) Command finished (0 sec)
(Thu Nov 08 06:19:17 2018)
v.info <http://v.info> map=geotechNov8@Toronto
±---------------------------------------------------------------------------+
| Name: geotechNov8
|
| Mapset: Toronto
|
| Location: Toronto
|
| Database: C:\Users\Francois
Chartier\Documents\grassdata |
| Title:
|
| Map scale: 1:1
|
| Name of creator: Francois Chartier
|
| Organization:
|
| Source date: Thu Nov 08 06:06:56 2018
|
| Timestamp (first layer): none
|
|----------------------------------------------------------------------------|
| Map format: native
|
|----------------------------------------------------------------------------|
| Type of map: vector (level: 2)
|
|
|
| Number of points: 188692 Number of
centroids: 0 |
| Number of lines: 0 Number of
boundaries: 0 |
| Number of areas: 0 Number of
islands: 0 |
| Number of faces: 0 Number of
kernels: 0 |
| Number of volumes: 0 Number of holes:
0 |
|
|
| Map is 3D: Yes
|
| Number of dblinks: 1
|
|
|
| Projection: UTM (zone 17)
|
|
|
| N: 4870782 S: 4825713
|
| E: 651697 W: 609201
|
| B: 0 T: 352
|
|
|
| Digitization threshold: 0
|
| Comment:
|
|
|
±---------------------------------------------------------------------------+
(Thu Nov 08 06:19:18 2018) Command finished (0 sec)

N �n�r����)em�h�yhiם�w^���

Virus-free. www.avast.com

So i rerun v.vol.rst with new g.region -p3

C:>g.region -p3

projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700

top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally worked with 200 m of min spacing. as you can see the majority of the points are excluded.
I am using 180k points over a 40 km 40 km domain.
I have not set any smoothing parameters. also using the default tension parameters and as data points are very close vertically (every m or less)
Thanks

(Wed Nov 14 20:50:41 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=0.5 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:50:50 2018) Command finished (8 sec)
(Wed Nov 14 20:51:08 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=5 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:51:17 2018) Command finished (8 sec)
(Wed Nov 14 20:51:25 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=20 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:51:34 2018) Command finished (8 sec)
(Wed Nov 14 20:51:46 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=50 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:51:59 2018) Command finished (12 sec)
(Wed Nov 14 20:52:11 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=70 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:52:20 2018) Command finished (8 sec)
(Wed Nov 14 20:55:19 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=100 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Wed Nov 14 20:55:28 2018) Command finished (8 sec)
(Wed Nov 14 20:55:46 2018)
v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 segmax=10 npmin=20 npmax=100 dmin=200 elevation=geotechnov8nov14
188692 records selected from table
WARNING: Some points outside of region – will ignore…
Processing all selected output files will require 24480 bytes of disk space for temp files
WARNING: There are points outside specified 2D/3D region–ignored 3533 points (total points: 188692)
WARNING: Points are more dense than specified ‘DMIN’–ignored 175580 points (remain 13112)
WARNING: Unable to create <(null)> raster map without cross_input raster map being specified
Finished interpolating
3D raster map created
The number of points in vector map is 188692
The number of points outside of 2D/3D region 3533
The number of points used (after reduction) is 9579
(Wed Nov 14 20:55:58 2018) Command finished (12 sec)

Virus-free. www.avast.com

Le mer. 14 nov. 2018 à 20:40, Francois Chartier <fra.chartier@gmail.com> a écrit :

good point. i created the 3d raster before. see g.region -p3 below.
I will rerun v.vol.rst with the higher 3d g.region resolution, and keep increasing the dmin until it runs.

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

Virus-free. www.avast.com

Le mer. 14 nov. 2018 à 09:38, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 14/11/18 01:28, Francois Chartier wrote:

Hi,

v.vol.rst starts working when npmin is 100 m or more. I dont believe
that this algorythm only works with data points spaced by 100 m that
does not make sense. is there a max total number for a dataset? is it
because i have too few rows and columns?
see metadata below. i also showed a lower dmin of 0.9. g.region is
printed at the end of the email

Your g.region output does not correspond to the region that was set when
you ran v.vol.rst as the map created has a resolution of 500 in x and y
direction, but your region says 10.

Could you provide the output of g.region -p3 to also get the 3D settings ?

I don’t have an exact idea, but the map you created has a resolution of
500 x 500 x 176, so maybe if you have a point per meter this just means
that the number of points you have per target pixel is much too high.

Maybe you need to think about the appropriate 3D region first and make
sure to set that before running v.vol.rst ?

Moritz

±---------------------------------------------------------------------------+
|
|----------------------------------------------------------------------------|
|
|
| Type of Map: raster_3d Number of Categories: 0
|
| Data Type: FCELL
|
| Rows: 90
|
| Columns: 85
|
| Depths: 2
|
| Total Cells: 15300
|
| Total size: 48229 Bytes
|
| Number of tiles: 4
|
| Mean tile size: 12057 Bytes
|
| Tile size in memory: 15480 Bytes
|
| Number of tiles in x, y and z: 2, 2, 1
|
| Dimension of a tile in x, y, z: 43, 45, 2
|
|
|
| Projection: UTM (zone 17)
|
| N: 4870782 S: 4825713 Res: 500.76666667
|
| E: 651697 W: 609201 Res: 499.95294118
|
| T: 352 B: 0 Res: 176
|
| Range of data: min = -1.17721057 max = 89.22615051
|
|
|
| Data Source:
|
|
|
|
|
|
|
| Data Description:
|
| generated by v.vol.rst
|
|
|
| Comments:
|
| v.vol.rst --overwrite input=“geotechNov8@Toronto” wcolumn=“dbl_2”
te\ |
| nsion=40. smooth=0.1 segmax=50 npmin=200 npmax=700 dmin=100
wscale=1\ |
| .0 zscale=1.0 elevation=“geotechnov8”
|
|
|
±---------------------------------------------------------------------------+
(Tue Nov 13 19:18:12 2018) Command finished (0 sec)

i have also tried with low dmin of 0.9 m:

(Tue Nov 13 19:22:49 2018)
v.vol.rst --overwrite input=geotechNov8@Toronto wcolumn=dbl_2 npmin=60
npmax=100 dmin=0.9 elevation=geotechnov13
188692 records selected from table
WARNING: Some points outside of region – will ignore…
ERROR: Points are too concentrated – please increase DMIN
(Tue Nov 13 19:23:00 2018) Command finished (10 sec)

METADATA of Vector points

Thu Nov 08 06:06:56 2018 |
| Timestamp (first layer): none
|
|----------------------------------------------------------------------------|
| Map format: native
|
|----------------------------------------------------------------------------|
| Type of map: vector (level: 2)
|
|
|
| Number of points: 188692 Number of centroids: 0
|
| Number of lines: 0 Number of boundaries: 0
|
| Number of areas: 0 Number of islands: 0
|
| Number of faces: 0 Number of kernels: 0
|
| Number of volumes: 0 Number of holes: 0
|
|
|
| Map is 3D: Yes
|
| Number of dblinks: 1
|
|
|
| Projection: UTM (zone 17)
|
|
|
| N: 4870782 S: 4825713
|
| E: 651697 W: 609201
|
| B: 0 T: 352
|
|
|
| Digitization threshold: 0
|
| Comment:
|
|
|
±---------------------------------------------------------------------------+
(Tue Nov 13 19:25:30 2018) Command finished (0 sec)

g.region - p

projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
nsres: 10
ewres: 10
rows: 3630
cols: 4250
cells: 15427500

Le ven. 9 nov. 2018 à 07:16, Francois Chartier <fra.chartier@gmail.com
mailto:[fra.chartier@gmail.com](mailto:fra.chartier@gmail.com)> a écrit :

does anybody know how to resolve this?

On Thu, Nov 8, 2018, 06:23 Francois Chartier <fra.chartier@gmail.com
mailto:[fra.chartier@gmail.com](mailto:fra.chartier@gmail.com) wrote:

Hi,

I am trying to use V.VOL.RST to interpolate particle size for
soil samples. i obtain the error message to increase DMin.
unfortunately i have a data point every meter vertically and a
total of 190K. if grass is asking to increase DMIN, which i
have increased to 30 m to try to see if this was the pb, can I
resolve this by reducing the Segment size?

  • COMMAND OUTPUT*
    (Thu Nov 08 06:17:32 2018) Command finished (10 sec)
    (Thu Nov 08 06:20:40 2018)
    v.vol.rst input=geotechNov8@Toronto wcolumn=dbl_2 npmin=50
    npmax=200 dmin=30 elevation=Geotech3DNov8
    188692 records selected from table
    WARNING: Some points outside of region – will ignore…
    ERROR: Points are too concentrated – please increase DMIN
    (Thu Nov 08 06:20:51 2018) Command finished (10 sec)

METADATA
Thu Nov 08 06:11:32 2018) Command finished (0 sec)
(Thu Nov 08 06:19:17 2018)
v.info <http://v.info> map=geotechNov8@Toronto
±---------------------------------------------------------------------------+
| Name: geotechNov8
|
| Mapset: Toronto
|
| Location: Toronto
|
| Database: C:\Users\Francois
Chartier\Documents\grassdata |
| Title:
|
| Map scale: 1:1
|
| Name of creator: Francois Chartier
|
| Organization:
|
| Source date: Thu Nov 08 06:06:56 2018
|
| Timestamp (first layer): none
|
|----------------------------------------------------------------------------|
| Map format: native
|
|----------------------------------------------------------------------------|
| Type of map: vector (level: 2)
|
|
|
| Number of points: 188692 Number of
centroids: 0 |
| Number of lines: 0 Number of
boundaries: 0 |
| Number of areas: 0 Number of
islands: 0 |
| Number of faces: 0 Number of
kernels: 0 |
| Number of volumes: 0 Number of holes:
0 |
|
|
| Map is 3D: Yes
|
| Number of dblinks: 1
|
|
|
| Projection: UTM (zone 17)
|
|
|
| N: 4870782 S: 4825713
|
| E: 651697 W: 609201
|
| B: 0 T: 352
|
|
|
| Digitization threshold: 0
|
| Comment:
|
|
|
±---------------------------------------------------------------------------+
(Thu Nov 08 06:19:18 2018) Command finished (0 sec)

N �n�r����)em�h�yhiם�w^���

Virus-free. www.avast.com

On 15/11/18 03:06, Francois Chartier wrote:

So i rerun v.vol.rst with new g.region -p3

C:\>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally worked with 200 m of min spacing. as you can see the majority of the points are excluded.

I'm not familiar enough with the code of v.vol.rst, so I'll have to leave this to Helena and her team.

Sorry,
Moritz

Finally. I am was able to make v.vol.rst work.
How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.

Below I am viewing the data with Isosurface with the 3d viewer, under
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

image.png

Virus-free. www.avast.com

Le jeu. 15 nov. 2018 à 03:44, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 15/11/18 03:06, Francois Chartier wrote:

So i rerun v.vol.rst with new g.region -p3

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally
worked with 200 m of min spacing. as you can see the majority of the
points are excluded.

I’m not familiar enough with the code of v.vol.rst, so I’ll have to
leave this to Helena and her team.

Sorry,
Moritz

Hourrah Finally. I am was able to make v.vol.rst work.

How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.
Now the work begins.

attached I am viewing the data with Isosurface with the 3d viewer, under
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

Virus-free. www.avast.com

Le ven. 16 nov. 2018 à 23:20, Francois Chartier <fra.chartier@gmail.com> a écrit :

Finally. I am was able to make v.vol.rst work.
How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.

Below I am viewing the data with Isosurface with the 3d viewer, under
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

image.png

Virus-free. www.avast.com

Le jeu. 15 nov. 2018 à 03:44, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 15/11/18 03:06, Francois Chartier wrote:

So i rerun v.vol.rst with new g.region -p3

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally
worked with 200 m of min spacing. as you can see the majority of the
points are excluded.

I’m not familiar enough with the code of v.vol.rst, so I’ll have to
leave this to Helena and her team.

Sorry,
Moritz

(attachments)

vvolrst.gif

Hourrah Finally. I am was able to make v.vol.rst work.

How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.
Now the work begins.

I am viewing the data with Isosurface with the 3d viewer, under (cant forward image as too large for mail list)
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

THANK YOU for your help. will keep u posted on progress.

Virus-free. www.avast.com

Le ven. 16 nov. 2018 à 23:20, Francois Chartier <fra.chartier@gmail.com> a écrit :

Finally. I am was able to make v.vol.rst work.
How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.

Below I am viewing the data with Isosurface with the 3d viewer, under
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

image.png

Virus-free. www.avast.com

Le jeu. 15 nov. 2018 à 03:44, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 15/11/18 03:06, Francois Chartier wrote:

So i rerun v.vol.rst with new g.region -p3

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally
worked with 200 m of min spacing. as you can see the majority of the
points are excluded.

I’m not familiar enough with the code of v.vol.rst, so I’ll have to
leave this to Helena and her team.

Sorry,
Moritz

Hourrah Finally. I am was able to make v.vol.rst work.

How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.
Now the work begins.

I am viewing the data with Isosurface with the 3d viewer, under (cant forward image as too large for mail list)

View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

THANK YOU for your help. will keep u posted on progress

On Sat, Nov 17, 2018, 11:39 Francois Chartier <fra.chartier@gmail.com wrote:

Hourrah Finally. I am was able to make v.vol.rst work.

How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.
Now the work begins.

I am viewing the data with Isosurface with the 3d viewer, under (cant forward image as too large for mail list)
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

THANK YOU for your help. will keep u posted on progress.

Virus-free. www.avast.com

Le ven. 16 nov. 2018 à 23:20, Francois Chartier <fra.chartier@gmail.com> a écrit :

Finally. I am was able to make v.vol.rst work.
How it worked.
I made the resolution to be 1 m in the 3 directions, x,y,z directions with g.region.
I thought that perhaps due to the high density of points perhaps i needed to increase the resolution.

Below I am viewing the data with Isosurface with the 3d viewer, under
View tab->3D raster, → choose 3d raster → add isosurface, define the interval you want to see, and color set as constant (i used bgyr as the color, but everything turns out blue…).

image.png

Virus-free. www.avast.com

Le jeu. 15 nov. 2018 à 03:44, Moritz Lennert <mlennert@club.worldonline.be> a écrit :

On 15/11/18 03:06, Francois Chartier wrote:

So i rerun v.vol.rst with new g.region -p3

C:>g.region -p3
projection: 1 (UTM)
zone: 17
datum: nad83
ellipsoid: grs80
north: 4862000
south: 4825700
west: 609200
east: 651700
top: 250.00000000
bottom: 50.00000000
nsres: 10
nsres3: 504.16666667
ewres: 10
ewres3: 500
tbres: 1
rows: 3630
rows3: 72
cols: 4250
cols3: 85
depths: 200
cells: 15427500
cells3: 1224000

V.VOL.RST run (below) with increasing DMIN, from 0.5 to 200. finally
worked with 200 m of min spacing. as you can see the majority of the
points are excluded.

I’m not familiar enough with the code of v.vol.rst, so I’ll have to
leave this to Helena and her team.

Sorry,
Moritz