Hello everyone,
I’m using the 3D-Forest-Fragementation Modul developed by Vaclav and have produced a workflow for the calculation. It is working well and I’m getting plausible results. While applying this workflow for my whole study region (35 plots/regions) it only works for about 50 % of the plots. The others fail at the step where I use r3.count.categories. I can’t see the link respectively the difference for this error. That’s why am asking for a hint:
I’m running Grass 7.8.2 (64 bit), Python 3.7.0, wxPython 4.0.7 on Windows 10
The problem occurs while running this command:
"r3.count.categories input=ff_mean_131_2 output=ff_mean_131_2_count slices=ff_mean_131_2_slice --overwrite"
With this error:
"[…]
Raster map 22 Filename: ff_mean_131_2_slice_00022
Raster map 23 Filename: ff_mean_131_2_slice_00023
WARNING: ZSTD compression error -14: Unsupported frame parameter
ERROR: Error uncompressing raster data for row 43 of <ff_mean_131_2_slice_00010>
ERROR: An error occurred while running r.mapcalc with expression: ff_mean_131_2_count_0 = int(ff_mean_131_2_slice_00001 == 0) + […]"
For each failing plot the error occurs in this step. The slices seem to be generated correctly. I couldn’t see differences while displaying them or comparing the raster metadata.
In the different plot its always another slice (2D Raster) and another row where the uncompressing fails. I tried to reduce the plot-size and found out, that the error occurs always in the same row of a plot. If this row is excluded, it works fine.
That’s why I think it has nothing to do with missing space on disk, or not enough calculating capacity.
Has someone an idea what’s the problem? Thanks very much!
Greetings,
Olivier
Hi Olivier,
<Olivier.C.Canon@umwelt.uni-giessen.de> schrieb am Do., 16. Juli 2020, 15:38:
Hello everyone,
I’m using the 3D-Forest-Fragementation Modul developed by Vaclav and
have produced a workflow for the calculation. It is working well and
I’m getting plausible results. While applying this workflow for my
whole study region (35 plots/regions) it only works for about 50 % of
the plots. The others fail at the step where I use
r3.count.categories. I can’t see the link respectively the difference
for this error. That’s why am asking for a hint:
I’m running Grass 7.8.2 (64 bit), Python 3.7.0, wxPython 4.0.7 on Windows 10
The problem occurs while running this command:
“r3.count.categories input=ff_mean_131_2 output=ff_mean_131_2_count
slices=ff_mean_131_2_slice --overwrite”
With this error:
"[…]
Raster map 22 Filename: ff_mean_131_2_slice_00022
Raster map 23 Filename: ff_mean_131_2_slice_00023
WARNING: ZSTD compression error -14: Unsupported frame parameter
ERROR: Error uncompressing raster data
Did you copy by chance the data from a different machine?
This error comes to mind:
https://lists.osgeo.org/pipermail/grass-user/2019-March/080180.html
Best
markusN
for row 43 of
<ff_mean_131_2_slice_00010>
ERROR: An error occurred while running r.mapcalc with expression:
ff_mean_131_2_count_0 = int(ff_mean_131_2_slice_00001 == 0) + […]"
For each failing plot the error occurs in this step. The slices seem
to be generated correctly. I couldn’t see differences while displaying
them or comparing the raster metadata.
In the different plot its always another slice (2D Raster) and another
row where the uncompressing fails. I tried to reduce the plot-size and
found out, that the error occurs always in the same row of a plot. If
this row is excluded, it works fine.
That’s why I think it has nothing to do with missing space on disk, or
not enough calculating capacity.
Has someone an idea what’s the problem? Thanks very much!
Greetings,
Olivier
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hi Markus,
no, I’m working on the same machine all the time. As external input data I use point cloud data in las-format that were generated with drone deploy. I had some trouble with the point clouds in the beginning, but I managed to convert them and load them in grass. The processing of the point clouds (rasterization, calculation of fragmentation index) works well now. I also use the DTM from Dronedeploy as base raster, but that shouldn’t have an effect on the rasterized point cloud.
Zitat von Markus Neteler <neteler@osgeo.org>:
Hi Olivier,
<Olivier.C.Canon@umwelt.uni-giessen.de> schrieb am Do., 16. Juli 2020,
15:38:
Hello everyone,
I’m using the 3D-Forest-Fragementation Modul developed by Vaclav and
have produced a workflow for the calculation. It is working well and
I’m getting plausible results. While applying this workflow for my
whole study region (35 plots/regions) it only works for about 50 % of
the plots. The others fail at the step where I use
r3.count.categories. I can’t see the link respectively the difference
for this error. That’s why am asking for a hint:
I’m running Grass 7.8.2 (64 bit), Python 3.7.0, wxPython 4.0.7 on Windows
10
The problem occurs while running this command:
"r3.count.categories input=ff_mean_131_2 output=ff_mean_131_2_count
slices=ff_mean_131_2_slice --overwrite"
With this error:
"[…]
Raster map 22 Filename: ff_mean_131_2_slice_00022
Raster map 23 Filename: ff_mean_131_2_slice_00023
WARNING: ZSTD compression error -14: Unsupported frame parameter
ERROR: Error uncompressing raster data
Did you copy by chance the data from a different machine?
This error comes to mind:
https://lists.osgeo.org/pipermail/grass-user/2019-March/080180.html
Best
markusN
for row 43 of
<ff_mean_131_2_slice_00010>
ERROR: An error occurred while running r.mapcalc with expression:
ff_mean_131_2_count_0 = int(ff_mean_131_2_slice_00001 == 0) + […]"
For each failing plot the error occurs in this step. The slices seem
to be generated correctly. I couldn’t see differences while displaying
them or comparing the raster metadata.
In the different plot its always another slice (2D Raster) and another
row where the uncompressing fails. I tried to reduce the plot-size and
found out, that the error occurs always in the same row of a plot. If
this row is excluded, it works fine.
That’s why I think it has nothing to do with missing space on disk, or
not enough calculating capacity.
Has someone an idea what’s the problem? Thanks very much!
Greetings,
Olivier
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hello,
I solved my problem and wanted share the solution:
Updating Grass and ZSTD helped to remove the error code.
However, the resulting maps were empty. The problem seems to be the base raster I used in the steps before. I don’t know why 50 % of DTM caused the problems, as I couldn’t find any error in this data. But exporting them as Geopackage and reimporting in Grass solved the problem.
Zitat von Markus Neteler <neteler@osgeo.org>:
Hi Olivier,
<Olivier.C.Canon@umwelt.uni-giessen.de> schrieb am Do., 16. Juli 2020,
15:38:
Hello everyone,
I’m using the 3D-Forest-Fragementation Modul developed by Vaclav and
have produced a workflow for the calculation. It is working well and
I’m getting plausible results. While applying this workflow for my
whole study region (35 plots/regions) it only works for about 50 % of
the plots. The others fail at the step where I use
r3.count.categories. I can’t see the link respectively the difference
for this error. That’s why am asking for a hint:
I’m running Grass 7.8.2 (64 bit), Python 3.7.0, wxPython 4.0.7 on Windows
10
The problem occurs while running this command:
"r3.count.categories input=ff_mean_131_2 output=ff_mean_131_2_count
slices=ff_mean_131_2_slice --overwrite"
With this error:
"[…]
Raster map 22 Filename: ff_mean_131_2_slice_00022
Raster map 23 Filename: ff_mean_131_2_slice_00023
WARNING: ZSTD compression error -14: Unsupported frame parameter
ERROR: Error uncompressing raster data
Did you copy by chance the data from a different machine?
This error comes to mind:
https://lists.osgeo.org/pipermail/grass-user/2019-March/080180.html
Best
markusN
for row 43 of
<ff_mean_131_2_slice_00010>
ERROR: An error occurred while running r.mapcalc with expression:
ff_mean_131_2_count_0 = int(ff_mean_131_2_slice_00001 == 0) + […]"
For each failing plot the error occurs in this step. The slices seem
to be generated correctly. I couldn’t see differences while displaying
them or comparing the raster metadata.
In the different plot its always another slice (2D Raster) and another
row where the uncompressing fails. I tried to reduce the plot-size and
found out, that the error occurs always in the same row of a plot. If
this row is excluded, it works fine.
That’s why I think it has nothing to do with missing space on disk, or
not enough calculating capacity.
Has someone an idea what’s the problem? Thanks very much!
Greetings,
Olivier
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hi Olivier,
On Tue, Jul 21, 2020 at 8:39 PM <Olivier.C.Canon@umwelt.uni-giessen.de> wrote:
Hello,
I solved my problem and wanted share the solution:
Updating Grass and ZSTD helped to remove the error code.
Great news!
However, the resulting maps were empty. The problem seems to be the
base raster I used in the steps before. I don’t know why 50 % of DTM
caused the problems, as I couldn’t find any error in this data. But
exporting them as Geopackage and reimporting in Grass solved the
problem.
Apparently still something depending on the version of ZSTD in
combination with the operating system.
In case you come across a reproducible error, please let us know.
Markus