Clemens Raffler

@kufreu @josephholler thank you for the PRs concerning those issues! I just wanted to ask you to open one PR for each unique issue. This way it is way easier...

Don't worry - the PR is fine as it is. I am very happy to see contributions from other people here. I'll review the commits ASAP so that we can...

Thanks for raising this issue @spatialthoughts, I have gotten this request too. I think it would be a useful algorithm. I don't know if I have time to implement this...

Hi @guenterhack, Thank you very much for testing QNEAT3! I tested the parameters you used in your analysis and confirm this bug. It is related to the interpolation classes that...

Hi @FitzeFatze580, thanks for your post and the update on your viewpoint on this bug. From your second screenshot I can see the problem - and yes - I have...

Hi @josephholler! Thank you for your thoughts on the plugin wording - I definitely see why the renaming of the algorithms is beneficial for teaching purposes and I'm open to...

Hi, sorry for the delayed answer, my calender is a bit crammed these days ;) @Algorithm Names: I'm fine with the 'dash-less' approach. @Parameter Descriptions: +1 for me - very...

I have never encountered this problem but I am glad you found a way around - we can definitely change the default value of the tolerance parameter as you proposed...

@josephholler: This is a very good analysis of the problem: Due to the fact that you could implement this in a pyhton script (looping through points and then intersecting the...

Thanks for the heads up! The units can be looked up at the [official algorithm help page/documentation](https://root676.github.io/IsoAreaAlgs.html). But having a more detailed description in the short help string or parameter...