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

Headland covering #21

Open
giusetalarico opened this issue Sep 24, 2022 · 5 comments
Open

Headland covering #21

giusetalarico opened this issue Sep 24, 2022 · 5 comments
Labels

Comments

@giusetalarico
Copy link

giusetalarico commented Sep 24, 2022

It would be great to have a function that generates path in order to cover the headland too (I think to navigate through that after all the swaths are covered).
This would be absolutely important for larger headland such as tractor's (they have Turning Radius of 5-6 meters, at least)

@Gonzalo-Mier
Copy link
Member

Hi @giusetalarico, thanks for your contribution.

This will be in the next version of the library. I'll add a little scheme about what to expect for future releases. We release this package "soon" with the idea that it could be useful for some people to start using it in this state. But headland coverage is for sure something important for agriculture :)

@Gonzalo-Mier Gonzalo-Mier added the enhancement New feature or request label Sep 25, 2022
@vinnnyr
Copy link
Contributor

vinnnyr commented Nov 27, 2022

Just checking -- was this closed accidentally, or Is this still relevant?

@Gonzalo-Mier
Copy link
Member

Not accidentally, but not sure either if my decision was right. This library is part of my PhD and this is already solved on my private version. I have a delay on releasing code between the private and the public code.

On one hand, I don't want anybody to spend time resolving this. If they want, ok. But I think there are more productive things to do.
On the other hand, I don't have a release date, and closing the issue may lead to think that it's already solved.

@vinnnyr, what do you think? Do you have any advice?

@vinnnyr
Copy link
Contributor

vinnnyr commented Nov 28, 2022

Hm, I definitely fell into the camp of this:

closing the issue may lead to think that it's already solved.

But your rationale makes a lot of sense. Maybe we keep the issue open and add some sort of label. Maybe in-progress since you have it in progress on your private copy?

@Gonzalo-Mier
Copy link
Member

Thanks, let's do that.

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

No branches or pull requests

3 participants