Feature request #7066
Updated by Alexander Bruy about 6 years ago
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.
# 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
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