-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Two geometry columns not supported since 3.28 #55871
Comments
The geopackage format has a strict limitation of one geometry field per table. The older versions would just export the geometry as a string field. You could recreate the old behaviour using a tool like "refactor fields" from the processing toolbox and using an expression to export the geometry to a wkt string. |
Hello nyalldawson, thank you. |
Neither of those formats support multiple geometry columns either |
Ok, I open a new issue with vector-menu clipping and temporary layer. |
@sylviaobk - if you need two or more geometry columns in Geopackage, you will have to deposit your wish at the OGC and the Geopackage working group. QGIS cannot change specifications of data formats we use. |
probably not going to go much further, as this was already considered and rejected by the Geopackage working group: opengeospatial/geopackage#646 That said, I have been involved in discussions with other QGIS community members to implement that as an extension, but no news on that front for now |
Thank you very much for the insight. |
What is the bug or the crash?
QGIS 3.22 could handle 2 columns of geometry. Since QGIS 3.28 this is not possible anymore.
This is necessary to use another geometrytype for the same object. point for the center and polygon for the area.
Steps to reproduce the issue
To see how it should work open QGIS 3.22
Export successfull
Now do the same steps in QGIS 3.28
5. Add Postgis Layer flaeche.sql
6. Right mouseclick on layer and export - objects save as Geopackage.
error: Not supported type for field wkb_geometry_center
flaeche_sql.txt
Versions
QGIS-Version
3.22.11-Białowieża
QGIS-Codeversion
106d33d
Qt-Version
5.15.3
Python-Version
3.9.5
GDAL-Version
3.5.1
PROJ-Version
9.1.0
EPSG-Registraturdatenbankversion
v10.074 (2022-08-01)
GEOS-Version
3.10.3-CAPI-1.16.1
SQLite-Version
3.38.1
PDAL-Version
2.4.3
PostgreSQL-Client-Version
14.3
SpatiaLite-Version
5.0.1
QWT-Version
6.1.6
QScintilla2-Version
2.13.1
BS-Version
Windows 10 Version 2009
Aktive Python-Erweiterungen
attributeBasedClustering
2.2.1
bkggeocoder
1.3.3
drucker
3.1.0
geometry_paster
0.4
OSMDownloader
1.0.3
pluginbuilder3
3.2.1
postgis_geoprocessing
0.9
punkte_setzen
1.0
qdraw
3.0.2
spatial_filter
1.5
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.5
processing
2.12.99
sagaprovider
2.12.99
QGIS-Version
3.28.4-Firenze
QGIS-Codeversion
fd0fb72
Qt-Version
5.15.3
Python-Version
3.9.5
GDAL-Version
3.6.2
PROJ-Version
9.1.1
EPSG-Registraturdatenbankversion
v10.076 (2022-08-31)
GEOS-Version
3.11.1-CAPI-1.17.1
SQLite-Version
3.39.4
PDAL-Version
2.4.3
PostgreSQL-Client-Version
unknown
SpatiaLite-Version
5.0.1
QWT-Version
6.1.6
QScintilla2-Version
2.13.1
BS-Version
Windows 10 Version 2009
Aktive Python-Erweiterungen
attributeBasedClustering
2.2.1
bkggeocoder
1.3.3
drucker
3.1.0
geometry_paster
0.4
OSMDownloader
1.0.3
pluginbuilder3
3.2.1
postgis_geoprocessing
0.9
punkte_setzen
1.0
qdraw
3.0.2
spatial_filter
1.5
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
sagaprovider
2.12.99
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: