Closed josephholler closed 5 years ago
Hi @josephholler, I had a look into the issue - it was a wrong if statement. Could you please test the master version in this repo whether you still get the issue? Thx!
Yes, this fixed the error! Many thanks.
On Mon, Dec 10, 2018 at 9:16 PM Joseph Holler joseph@josephholler.com wrote:
I saw your code fix and it makes sense. The structure of if - else if - would have dropped the 0th record and every 1000th record thereafter. It was actually my students in an introductory GIS course who identified the issue while they were working on a final exam. I'm slammed with the work of grading the exam now, and will try the new code as soon as I can.
On Mon, Dec 10, 2018 at 2:23 PM Clemens Raffler notifications@github.com wrote:
Hi @josephholler https://github.com/josephholler, I had a look into the issue - it was a wrong if statement. Could you please test the master version in this repo whether you still get the issue? Thx!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/root676/QNEAT3/issues/10#issuecomment-445939542, or mute the thread https://github.com/notifications/unsubscribe-auth/AJkwf0AYbVVrmGb-Cv1VOwE7nXQEHLtNks5u3rTLgaJpZM4ZBGQI .
I'm running QGIS version 3.2.1 and QNEAT3 version 1.0.1 on Windows 10. I have noticed that OD Matrix from Layers algorithm always results in one fewer records than expected, and that the missing record is not always the same record. For example, given an input of 8 destination points and 11 origin points, the resulting table has 87 records, where 88 are expected. The algorithm dialogue says that the correct number of pairs (88) were processed. (Total number of OD-pairs processed: 88) This cannot be an error in the lines, origins, or destinations, because the missing pair is not the same and thus the missing pair has been correctly calculated in other iterations of running the algorithm or with different subsets of the data. I have not been able to determine a consistent pattern as to which record is dropped.
Thanks for this useful plugin!