# GNSS S-JTSK (EPSG 5514) projection problem

**URL:** <https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979>\
**Category:** Ask the Community\
**Tags:** gh-import\
**Created:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979 "2025-05-14T03:24:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979/1 "2025-05-14T03:24:31Z")

</div>

Hello,  
I use Qfield on Android with South S660 GNSS receiver which outputs WGS84 data. All my projects use EPSG 5514 projection. Lately ( a few months ) the positioning is about 1 meter off in bot coordinates. The project file has not changed, nor I did any changes to GPS settings, I just updated Qfield. I also tried connecting GPS directly to Qfield which resulted in location showing completely elswehere (another space dimension, probably). Is there anything else other than converting all projects to use EPSG4326 ? What exactly has changed ? Thanks, Tom

* * *

_Imported from [GitHub discussion](https://github.com/opengisch/qfield/discussions/2223) by @cz-ranger on 2021-10-12T13:51:09Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979/2 "2025-05-14T03:24:32Z")

</div>

cz-ranger , can you attach a screenshot of your positioning settings panel?

Ie:

 ![Screenshot_20211012-220425_QField Beta 2219](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/3ab08fa449448f2a16eeb9a6872f4e27276887e7.jpeg)

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/2223#discussioncomment-1465460) by @nirvn on 2021-10-12T15:04:54Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979/3 "2025-05-14T03:24:34Z")

</div>

This is the positioning setting using directly connected to GPS via Bluetooth (location totally off)

 ![Screenshot_20211013-104804](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/4f5f308de4317966ff27401015c4e1dfc392461f.jpeg)  
 ![Screenshot_20211013-105229](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/3531f864c2ed3bb3a3de3a10c08b898230e2ff63.jpeg)  
This is the position setting when using mock location via native app from South (LBS Manage). This works, but the position is consistently about 1m off in both x and y. This problem is exclusive to Qfield, in other mapping apps the location appears to be correct.  
 ![Screenshot_20211013-104623](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/99404834f298ffaf1a252ea13f1bd573474dea49.jpeg)  
 ![Screenshot_20211013-105405](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/30607880236f0e736eaac310d331e1414aa4541b.jpeg)

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/2223#discussioncomment-1469449) by @cz-ranger on 2021-10-13T09:04:35Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979/4 "2025-05-14T03:24:35Z")

</div>

Could you check whether the location appears to be correct if you set your project CRS to EPSG:4326 (ie WGS84)?

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/2223#discussioncomment-1469591) by @nirvn on 2021-10-13T09:26:29Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 03:24 UTC](https://community.qfield.org/t/gnss-s-jtsk-epsg-5514-projection-problem/979/5 "2025-05-14T03:24:37Z")

</div>

cz-ranger , I did a couple of tests locally. It could well be that your project’s datum transformations settings aren’t properly set.

If you open your project on QGIS and open the project properties’ transformation panel, you can add/edit the transformation maths used to go to/from EPSG:5514 to EPSG:4236 (WGS84, the position’s coordinates projection).

This transformation worked for me:

 ![image](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/5df76092421beb01a07c337b6f5ab7f7589d1dcc.png)

While the other ones would have test points not align as expected.

I suggest you give this a try. Also, give QField 2.0 beta 8 a try if you haven’t yet.

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/2223#discussioncomment-1470233) by @nirvn on 2021-10-13T11:38:26Z_
