-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
postgres provider: allow to load layers with polyhedral surfaces or TINs #2322
Conversation
is TRIANGLE already supported ? that's also an areal geometry |
about that test: it might be useful for it to allow changing connection parameters via an env variable (libpq standard variables could do, beside database name) -- is that test already run on "make check" ? |
4d479b8
to
fefe94d
Compare
@m-kuhn Is the postgres provider test is run during a pull request build ? It should fail since it now relies on new tables ... which should not be there without your manual intervention. Right ? |
@mhugo yes, they are run during pr builds. but since the db is recreated on every travis build, you can add your own extensions ( see https://github.com/qgis/QGIS/blob/master/ci/travis/linux/before_script.sh ) without my intervention. |
@m-kuhn ah nice! So my new tests have successfully passed :) |
@m-kuhn You added "Requires tests". Do you think this requires additional tests ? Or is it ok to merge before the freeze ? |
Thanks for the tests. Assigned @jef-n , he's most experienced with the postgres provider I think. |
The postgres provider is modified so that layers with TIN, PolyhedralSurface and Triangle geometries can be loaded. Geometries are converted to MultiPolygons (and Polygons for Triangles). The postgres test is completed to cover the loading of different types of layers
Back on this topic. |
Postgres provider: allow to load layers with polyhedral surfaces or TINs
This restores a hack that was introduced prior to geometry refactoring in order to be able to load TIN and polyhedral surfaces layers in QGIS (in 2D).
@jef-n @mhugent just to be sure it does not break anything else ...
Would there be any way to setup a postgis provider unit tests ?