Feature request #7066

Geoprocessing impossible if field names are too long

Added by Bernhard Ströbl about 4 years ago. Updated 4 months ago.

Status:Open Start Date:01/29/2013
Priority:Normal Due date:
Assigned to:- % Done:


Target version:Future Release - Lower Priority
Platform:any Resolution:
Platform version: Pull Request or Patch supplied:No
Status info: Tag:


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.
  1. more automatic: Truncate the problematic field names but make sure they are unique in the result
  2. more user-oriented: let the user assign an alias to the problematic fields and use this
  3. (best): combine both: use the alias and if none is given truncate


Updated by Jürgen Fischer almost 3 years ago

  • Target version changed from Version 2.0.0 to Future Release - Lower Priority

Updated by Giovanni Manghi 4 months ago

  • Category changed from fTools to Processing/QGIS

Also available in: Atom