-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core QGIS algorithm? #5
Comments
Hi, @ghtmtt. |
OK, could/should do you want to split the job in some ways? I can help if you want. Just tell me |
What needs to be done? Is there a description of the procedure somewhere? |
actually you just need to take the algorithm.py and make some small tweaks. we can start to do that on a fork and then make a pull request |
OK. You lead the way. |
Algorithm ready for PR: https://github.com/ghtmtt/QGIS/tree/processing_climb I removed the calling to drape alg (we are in core so it is due to the user to do that). But an exception is raised and in the help file it is written. I also added some tests. So, I'll wait for your green light to click on the PR button.. and of course kudos to you, not to me :) |
I have provided some comments and suggestions for your consideration. |
Been playing around with this, and works great. I know this may buck against QGIS' standard work flow, but I'm really digging how the Calculate Geometry plugin works: Click a button or two, and the relevant layer fields are updated in place. Super-handy when geometries are changing frequently, and I need to keep recalculating the new state. (It's a bit arduous to create a new layer, save it as the old layer, etc...) |
Hi @havatv I really really think that this plugin should go in core, of course if you agree.
Framework is easy, smooth and works super nice. What do you think about it?
The text was updated successfully, but these errors were encountered: