Request for Support – QField Compatibility with Binary Image Fields (PostgreSQL)

Ask the Community
1

Dear QField Team,

I am currently working on a project related to excavation documentation, where each feature in our PostgreSQL database needs to have an associated photo showing the excavation and its specifications.

In our online workflow, we successfully store these photos in a binary field within the PostgreSQL database, and everything functions correctly. However, we are facing a major limitation when using QField in offline mode:
QField does not currently support fields of type binary (bytea).

Our field engineers use QField to collect and draw excavation data in the field, which is later synchronized with the server. Since binary fields are not supported, images cannot be uploaded or viewed properly once synchronized.

Could you please advise if there are any planned updates or workarounds to support binary fields in QField?
Alternatively, we would appreciate any recommended methods for uploading and displaying images on the server side while maintaining a smooth synchronization workflow with PostgreSQL.

Thank you for your attention and support.

2

Dear @wasfy_mohammed as of now, we record attachments via string fields.

It is not so easy to do what you want. As of now you would have to rely on SDK QFieldCloud

GeoPackage supports blobs as binary fields so potentially, we could develop something that supports what you want. It would be quite a development needed in QFS/QFC and QField.

If you are interested in sponsoring this feature, we would very much welcome this. Perhaps you could also create an idea on the Idea’s platform?

Thanks a lot!