2

I'm trying to convert a postgis table to an ESRI FileGeodatabase with a nightly build of QGIS, using Save As which utilises OGR.

One of the fields is a text field with > 255 characters. I have noticed that the field was truncated to 255 characters and then QGIS did not export the records which had more than 255 characters in the field. I then found this part of the QGIS code which seems to truncate String fields to 255 characters.

I understand that this has always been a limitation for Shapefiles, but it is not for file geodatabases, so it seems bizarre to truncate all text even when the provider supports it. Or is there some other limitation I should be aware of?Maybe should go on QGIS-dev but thought I would get folks' view here first.

  • 1
    This is definitely something to discuss on the qgis-dev mailinglist (or if you feel confident, even propose a change on this line as pull request on github). – Matthias Kuhn Mar 6 '18 at 14:06
  • Technically, the dBase-III limit is 254. – Vince Mar 6 '18 at 14:32
  • 1
    I had always assumed all the shapefile limitations were ported forward to the FileGeoDatabase spec but as it is a closed format it's hard to say. – Ian Turton Mar 6 '18 at 15:25
  • @IanTurton If you look at the published API, it's obvious that file geodatabase does not, did not, and never had any of the baggage of shapefiles. I fear your assumption falls under the famous caveat in that regard. – Vince Mar 7 '18 at 0:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.