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.

Sign up for GitHub

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

Jump to bottom

prevent warning twice about bad extent #178

Open

mdsumner opened this issue Nov 11, 2022 · 0 comments

Member

mdsumner commented Nov 11, 2022

we call feature count before executesql, when setting up 'ij' - so internal calls should be able to silence any messaging

see #171 to trigger the warning comment in

vapour/src/00_geometry.cpp

Line 178 in d247955

    
           // we get two warnings if the extent is poorly ordered, see 171 but I don't want to fix that atm

mdsumner changed the title ~~prevent warning about bad extent twice~~ prevent warning twice about bad extent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment