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
[processing][needs-docs] allow to exclude features without category from GRASS export #9003
Conversation
@alexbruy totally fine! |
@nyalldawson, @gioman if you are ok with these changes I will merge it and backport to 3.4 today |
No strong opinions here - if @gioman is happy, I'm happy! |
yes, I think that the flag was added without fully understanding the consequences. |
@gioman so using it by default is ok for you (this way algorithms behavior will be the same as in previous versions) or better to turn it off by default? |
@alexbruy the "-c" flag must not be used by default when exporting vectors from GRASS/Processing. It should eventually be possible to enable it (this is what my PR did, and I think also yours). In QGIS 2 this flag was not used (and had no option to enable it, as far as I remember). |
@gioman I know. But in previous QGIS 3.x releases it was used and probably some users now rely on this wrong behavior. I'm not sure if we should break it now. Personally I'm fine with disabling |
to me it was added by mistake, not thinking about the consequences
I doubt, in my opinion this option leads to a wrong output most of the times. |
Description
Ressurects #8419. IMHO this is quite important fix and would be nice to have in both 3.6 and 3.4 LTR.
As per #8419 while exporting GRASS vectors to a simple features format using
v.out.ogr
now the-c
flag is always used, and this is not expected as it can lead to wrong/unexpected results. On other hand, to keep API stable and produce same results as older 3.x version this PR keeps-c
flag enabled by default, allowing user to change it.If we argee that better to disable
-c
flag by default, I will update all tests accordingly.@gioman hope you are fine with it.
Checklist
fixes #11111
in the commit message next to the description[FEATURE]
in the commit message[needs-docs]
in the commit message and contain sufficient information in the commit message to be documentedscripts/prepare-commit.sh
script before each commit