Feature request #7066
Geoprocessing impossible if field names are too long
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Processing/QGIS | ||
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Easy fix?: | No | Copied to github as #: | 16150 |
Description
currently geoprocessing (e.g. Intersect, Union) aborts if field names in one of the input layers are too long
An error message is returned to the user. However there are cases where naming the field is not under the control of the user (no write access to shapefiles, only SELECT rights on PostGIS tables etc.). This is a bad user experience and absolutely not necessary because IMHO there are two possible solutions.
An error message is returned to the user. However there are cases where naming the field is not under the control of the user (no write access to shapefiles, only SELECT rights on PostGIS tables etc.). This is a bad user experience and absolutely not necessary because IMHO there are two possible solutions.
- more automatic: Truncate the problematic field names but make sure they are unique in the result
- more user-oriented: let the user assign an alias to the problematic fields and use this
- (best): combine both: use the alias and if none is given truncate
History
#1
Updated by Jürgen Fischer over 10 years ago
- Target version changed from Version 2.0.0 to Future Release - Lower Priority
#2
Updated by Giovanni Manghi almost 8 years ago
- Category changed from 44 to Processing/QGIS
#3
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#4
Updated by Alexander Bruy almost 7 years ago
- Resolution set to fixed/implemented
- Status changed from Open to Closed
- Description updated (diff)
Fixed in master. You can save to Geopackage and this is a default behavior.