Bug report #21969

v.net.path is not considering the

Added by Sergio Antonio over 1 year ago. Updated over 1 year ago.

Status:Closed
Priority:Normal
Assignee:-
Category:GRASS
Affected QGIS version:3.4.6 Regression?:No
Operating System:Windows 10 Easy fix?:No
Pull Request or Patch supplied:No Resolution:not reproducable
Crashes QGIS or corrupts data:No Copied to github as #:29784

Description

v.net.path is not considering the node cost variable.
QGIS 3.4.7

node cost.png (20.9 KB) Sergio Antonio, 2019-05-02 03:10 PM

History

#1 Updated by Giovanni Manghi over 1 year ago

  • Subject changed from v.net.path is not considering the node cost variable to v.net.path is not considering the
  • Status changed from Open to Feedback
  • Easy fix? changed from Yes to No

Can you more specific? Is the parameter missing from the tool GUI? What is the exact parameter name("node cost variable" is not listed here https://grass.osgeo.org/grass76/manuals/v.net.path.html)?

#2 Updated by Sergio Antonio over 1 year ago

Giovanni Manghi wrote:

Can you more specific? Is the parameter missing from the tool GUI? What is the exact parameter name("node cost variable" is not listed here https://grass.osgeo.org/grass76/manuals/v.net.path.html)?

This problem has been intermittent.
The given data complies with that requested by v.net.path tool (input vector line - arcs, center points, file containing star and end points, threshold for containing centers, arc forward/both directions, arc backward direction, node cost). Other fields: default value.
More details:
a) The tool works well when I do not use "node cost".
b) The tool has failed when a new point is added to the existing ones using QGIS vector editing. It does not consider the cost of the new point.
c) From time to time, QGIS informs you that an error has occurred and that it will close. But, when I click OK the QGIS does not close. The v.net.path tool terminates the calculations and creates the output file and layer.
d) Please note the figure.

#3 Updated by Giovanni Manghi over 1 year ago

b) The tool has failed when a new point is added to the existing ones using QGIS vector editing. It does not consider the cost of the new point.

so if you load a layer, open v.net.path, use the layer as input it works,

if you load it, edit it, use it as input then the edited features are not taken into account,

correct?

#4 Updated by Sergio Antonio over 1 year ago

Giovanni Manghi wrote:

b) The tool has failed when a new point is added to the existing ones using QGIS vector editing. It does not consider the cost of the new point.

so if you load a layer, open v.net.path, use the layer as input it works,

if you load it, edit it, use it as input then the edited features are not taken into account,

correct?

Yes. Correct.

#5 Updated by Giovanni Manghi over 1 year ago

Yes. Correct.

what if you add to the project (again) the edited layer (and give it a different name) and use it in the tool?

#6 Updated by Sergio Antonio over 1 year ago

Giovanni Manghi wrote:

Yes. Correct.

what if you add to the project (again) the edited layer (and give it a different name) and use it in the tool?

I followed your suggestions, but the results are inconclusive.
Sometimes it works well, but sometimes it does not.
Detail: All shape files (points and lines) were generated in QGIS 2.14.18.
Important: everything started working reasonably well when I created a NEW file (points.shp) in QGIS 3.4.7 to replace the original file from QGIS 2.14.18.

#7 Updated by Giovanni Manghi over 1 year ago

Important: everything started working reasonably well when I created a NEW file (points.shp) in QGIS 3.4.7 to replace the original file from QGIS 2.14.18.

weird, but if true/confirmed (and I can't see why not) then it should really not be an issue of just this specific tool, maybe is a more general problem.

#8 Updated by Sergio Antonio over 1 year ago

Giovanni Manghi wrote:

Important: everything started working reasonably well when I created a NEW file (points.shp) in QGIS 3.4.7 to replace the original file from QGIS 2.14.18.

weird, but if true/confirmed (and I can't see why not) then it should really not be an issue of just this specific tool, maybe is a more general problem.

Yes, very very strange, I have to admit.
On the other hand, version 3.x.x is getting very good, including the GRASS tools.
Please consider it resolved, at least for now. Thank you.

#9 Updated by Giovanni Manghi over 1 year ago

  • Resolution set to not reproducable
  • Status changed from Feedback to Closed

Also available in: Atom PDF