Joseph Holler

I wondered about that: self-admittedly this is the first time I've tried submitting major changes to another person's GitHub repository. I have to move on to other projects as the...

Thanks! One of the things you did not want to change (output field names) should be in dc51e6a , and maybe another in 1efb830

@Sohaahm, it's better to ask a question like this as a new issue, or to look for the most related issue to reply to. This thread is for a pull...

I've been looking at this same issue. The problem is that the TIN will create very long edges at the boundaries of your network and in any place where the...

Can the title of the issue be changed to reflect the problem? The problem isn't Vienna, it's TIN interpolation of network vertices into a cost surface

Try projecting all of your inputs (network layer and start points layer) to a projected coordinate system using meters as its linear units, and set the QGIS Project CRS to...

Thanks for looking at this! We probably should have divided all the suggestions into different pull requests: I hope you don't mind parsing the one request. Algorithm names: agreed, keep...

The three layers in your zip file are all using different coordinate reference systems, and for best results all layers should use the same projected coordinate reference system. Try reprojecting...

Responding to point 1: I've been interested in this as well. The current programming framework for QNEAT3 does not support it. From my understanding: The QNEAT3 Polygon and Contour outputs...

To follow up on this, the algorithms currently ask for an input "unique point ID field", which cannot be meaningful the way the algorithms work. Can this input be removed...