"Post-processing: Failed!" in Windows 7, if the Segment map or road centre line box is checked

[samuto]

Hello Jorge:

The depthmapX remote is able to run if the (Segment map or road centre line) is unchecked. However, if it is checked, the analysis will return the error like this:
Running analysis for map layer '2832_spm_pr_op02_seg':
analysis type - segment input
distance - angular
metric radius - 800,1200,400
calculate choice
calculate NACH and NAIN

Start: 06/12/2018 10:39:58
...
Finish: 06/12/2018 10:39:59
Post-processing: Failed!
Total running time: 0:00:00.994000

my desktop setting and software configuration are as follow:
qgis version: 2.18.24
depthmapXnet version: 0.35

Best,
Tao

[jorgegil]

Hi @samuto ,

Apologies for the very belated response. I need to look into this issue by testing on a machine with your setup. Can you please send me a sample file (email).

thanks,
Jorge

[samuto]

Hi Jorge,

I was using the office computer and the files are in the office server, many of the office computers had this issue. Since I left the office this year, I have no access to the file and the computer any more. You may ask Ioanna or Sujin to give the sample file to you.

Regards,
Tao

[Anafi]

@jorgegil @samuto It seems that the problem is related with the version of QGIS. I had similar issues in Windows 10 with QGIS versions 2.18.24 - 2.18.28. When the RCL option was ticked the analysis was failing. However, when using QGIS 2.18.18 the analysis was successful.

[rumeysabayar]

Hello,

Is there any update about this issue? I am experiencing the same problem with QGIS 3.30.0 in Windows 10 64-bit. It doesn't matter with axial or segment data. I also tried with the older version mentioned here but the result remains the same.

[Stanistheman-design]

Hello,

Is there any update about this issue? I am experiencing the same problem with QGIS 3.30.0 in Windows 10 64-bit. It doesn't matter with axial or segment data. I also tried with the older version mentioned here but the result remains the same.

Hello,

Is there any update about this issue? I am experiencing the same problem with QGIS 3.30.0 in Windows 10 64-bit. It doesn't matter with axial or segment data. I also tried with the older version mentioned here but the result remains the same.

Did you get any updates?