Skip to content
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

Make SOS-tools available in grass-addons #43

Open
ninsbl opened this issue May 8, 2020 · 4 comments
Open

Make SOS-tools available in grass-addons #43

ninsbl opened this issue May 8, 2020 · 4 comments
Assignees

Comments

@ninsbl
Copy link
Contributor

ninsbl commented May 8, 2020

Would be good to see those tools in https://github.com/OSGeo/grass-addons/tree/master/grass7

This may require some changes for Python 3?

@pesekon2 pesekon2 self-assigned this May 8, 2020
@pesekon2
Copy link
Owner

pesekon2 commented May 8, 2020

Uf. Yes, true. I remember I wanted to solve one issue somewhere and then push it to the official repository.

Well, as now I should also rewrite it to Python 3, maybe it's finally the right time to do that.

@pesekon2
Copy link
Owner

pesekon2 commented May 8, 2020

Issue #44 opened for the part of Python 3.

@pesekon2
Copy link
Owner

I remember I wanted to solve one issue somewhere and then push it to the official repository.

The blocking issue is #46. After solving that one, the modules could be made available in the official GRASS GIS AddOns repo.

@pesekon2
Copy link
Owner

Although there is still a lot of things to improve, I have solved all the blocking issues. Shall I move it to the official AddOns repository? How am I supposed to do it when there is a library needed for modules going into different directories (v.*, r.*, t.*)?

Also, I think that I will keep a schizophrenic way of keeping this repo alive with all minor issues and proposals in parallel to the official GRASS AddOns repo. I hope it's fine, although not very systematic.

@ninsbl: Don't you use these modules in some processing chains to test everything? I have tested everything in a dummy manual way, but to be sure that something hidden didn't get broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants