Improvements to Processing:qgis:network analysis

[qgib]

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 16011

Redmine category:processing/qgis

---

I suggest to:

• display start and end point for shortest path (point to point)
• send a message to the user in case something goes wrong (e.g. tolerance is too low, so no path is generated)
• default speed (5) seems to low
• if the projection is in degrees (e.g. EPSG:4326), and the user chooses a too high tolerance (e.g. 2 degrees), the path is apparently not computed; better warn the user about this.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0

[qgib]

Author Name: Paolo Cavallini (@pcav)

---

• assigned_to_id removed Victor Olaya
• description was changed from I suggest to:

• display start and end point for shortest path (point to point)
• send a message to the user in case something goes wrong (e.g. tolerance is too low, so no path is generated)
• default speed (5) seems to low
• if the projection is in degrees (e.g. EPSG:4326), and the user chooses a too high tolerance (e.g. 2 degrees), the path is apparently not computed; better warn the user about this. to I suggest to:
• display start and end point for shortest path (point to point)
• send a message to the user in case something goes wrong (e.g. tolerance is too low, so no path is generated)
• default speed (5) seems to low
• if the projection is in degrees (e.g. EPSG:4326), and the user chooses a too high tolerance (e.g. 2 degrees), the path is apparently not computed; better warn the user about this.

[alexbruy]

Displaying start and end points is not possible as Processing tools should run in non-inetractive mode. Although new point layer output can be added to store these points but personally I'm not sure this is useful as start and end points can be easily retrieved from the generated shortest path layer.

Algorithms throw exception if there is no route from start to end point which is the canonical way for Processing tools to report errors.

In the master default speed set to 50 km/h.

Seems this can be closed.

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.