[Processing OMBB] ID parent missing #4694
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add between/not between to numerical fields in select by form
…funded by Kartoza
Some WFS servers like QGIS servers can expose GML3 output format for GetFeature requests, which enable to retrieve curve geometries, instead of linearized ones with the default GML2 output format. So use GML3 when advertized, and that no explicit outputFormat is passed in the URI. Cherry-picked from commit 852f01b
[WFS provider] Select GML3 output format for WFS 1.0 when available
(cherry-picked from f3e90f1)
[2.18] OGR data provider: use transactions when changing attributes and geometries (if possible) (#16216)
Starting with GDAL 2.2, there are 2 concepts: unset fields and null fields whereas previously there was only unset fields. For QGIS purposes, both states (unset/null) are equivalent. Cherry-picked from 47dd83d
This change allows customised legends within composer templates to be correctly restored when creating a new composition from the template in a different project. The legend layers will be attached to any loaded layers with a matching data source as the layer from the original template composition. Fix #2738 Sponsored by ENEL, on behalf of Faunalia
…tion Sponsored by ENEL, on behalf of Faunalia
[composer] Restore legend customisation from composer templates (Fix #2738)
[Processing] Add SAGA LTR support in 2.18
* Set a name to the raster resampling dialog * Fix "Configure container" dialog
Also add a comment about lack of support in GDAL up to 2.2.x for service specification in datasource uri Ref #16626
Fix tile render mode not applied in 2.18 server
Works around GDAL limitation reported in: https://trac.osgeo.org/gdal/ticket/6910 Ref #16625 Closes #16626
MSSQL provider fixes
…tputValues Fixes #16618 Processing rscripts: cannot concatenate 'str' and 'NoneType' objects
Only enabled when ENABLE_PGTEST is set Includes test for dbname-less URI and service-only URI (ref #10600 ref #16625 ref #16626) The test connects to the `qgis_test` database, or what the QGIS_PGTEST_DB variable requests (as per tests/README.md) A raster table is added to the test postgis setup script, for use by this new test.
Hopefully fixes the new DBManager tests
update Processing SAGA provider for 2.18
update Processing OTB provider for 2.18
Was tested with python2, let's see if it fixes python3 too
2.18 Backport Ref #15910
…MultiCurve_CompositeCurvePropertyType type as multilinestring layers (#16675)
|
@GlaDal is it necessary a rebase? |
Add test for DBManager's PostGIS connector and plugin
|
@GlaDal please open this as a feature request over at https://issues.qgis.org . A pull request is only used for submitting code to QGIS. |
|
@GlaDal incidentally, if you try QGIS 3.0 pre-release, this should already be fixed. You'll just need a build from > 1 week ago as processing is being reworked at the moment and only a small subset of algorithms are currently available. |
|
@luipir @nyalldawson You're right. I'm discovering github's world and I've posted too fast ! Sorry for that ! Thanks at all ! |
|
@nyalldawson I tested OMBB in Qgis 3.0 pre-release : fantastic ! Ok, next time, I'll take time for posting on the right place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Could be nice to keep at least a column "ID_parent" from source layer after processing OMBB (the must could be to have the possibility to choose the ID column from the source table) ; It would offer the possibiilty to join the processed layer with the source layer thanks to the ID parent column.
Here an example of use : https://archeomatic.wordpress.com/2014/12/05/whitebox-gat-3-2-qgis-2-x-automatiser-le-calcul-de-longueur-et-dorientation-dun-polygone/