I created a project in QGIS with project CRS in EPSG:3857, packed it for Qfield with Qfield Sync plugin and saved it to my Android device. When I open the project there with Qfield and activate GPS, my position shows in a completely wrong place: northwest of Svalbard islands somewhere in the Ocean (see first screenshot below). I am, however, in Zurich, Switzerland.

Using other apps (like OsmAnd) on the same phone with same GPS receiver, I get the correct position. So the problem is obviously with Qfield.

If I zoom to my point layer an then zoom out, I realise that the points are way off the OSM basemap: see second screenshot below. My region of interest shows up, GPS position is somewhere down. When I pan to the GPS position (blue dot), I have to heavily zoom in to see the dynamic OSM basemap. So my point layer + the saved static raster basemap is completely wrong as concerns position and scale. So the problem seems to be connected with this one here.

I have no clue what went wrong. How to solve the problem?

My position as it appears when activating GPS. Zooming in to the blue dot does not help: enter image description here

Region of interest with the static raster OSM basemap, saved as gpkg file by the Qfield Sync plugin on the upper part; my position (blue dot) at the lower part. The dynamic OSM basemap (XYZ tiles) does not show as it is zoomed out too much: enter image description here

Zooming in the the GPS position does not solve the problem - it still shows a location NW of Svalbard: enter image description here

  • I remember a bug in some previous QGIS versions where points at certain scales were incorrectly displayed at this location (or the basemap was misplaced, cant tell). Maybe it is related to it, or caused in an underlying library. Does your location display correctly if you zoom to zurich?
    – MrXsquared
    Jun 7 at 7:34
  • No, that doesn't solve the problem. The problem you mentioned is the one that shows wrong position when zooming out and using EPSG:4326 as project CRS?
    – Babel
    Jun 7 at 7:38

1 Answer 1


What exactly caused the problem is still unclear to me, however, I found a solution by simply deinstalling and installing QField again. I use the same Qfield version as before (2.1.4), so there seems to be an issue with the updated Qfield version.

Your Answer

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.