# Device orientation accuracy in Lightship Maps implementation?

**URL:** <https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028>\
**Category:** Technical Support\
**Tags:** lightship-maps\
**Created:** [July 10, 2024, 9:42pm UTC](https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028 "2024-07-10T21:42:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paradowski\_Creative](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/paradowski_creative/32/811_2.png) [@Paradowski\_Creative](https://forum.8thwall.com/u/Paradowski_Creative)\
**Post date:** [July 10, 2024, 9:42pm UTC](https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028/1 "2024-07-10T21:42:01Z")

</div>

Can anyone explain why GPS + device orientation is less accurate in Lightship Maps versus Google Maps? Location itself works well, but while Google Maps sets the direction I’m facing perfectly, Lightship Maps shows a lot of random, floating rotation and directionality in the avatar - and I see this whether I’m using the 8th Wall React Scavenger Hunt example or the native Pokemon Go app itself.

Because it’s in Niantic’s flagship native app, I am guessing this can’t really be mitigated? But just wanted to confirm. Let me know, thanks!

---

<div class="post-metadata">

**Author:** ![TonyT](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/tonyt/32/88_2.png) [@TonyT](https://forum.8thwall.com/u/TonyT)\
**Post date:** [July 10, 2024, 10:22pm UTC](https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028/2 "2024-07-10T22:22:25Z")

</div>

By default, not all browser have access to compass, so I believe our maps module is orienting Doty based on change in location. If you start to walk down the street, for example, Doty will face the direction you are moving.

Check out this sample project where compass is explicitly requested (there is an additional browser prompt required, at least on iOS)

This example shows aframe + compass + Niantic Map. (click the compass in the top-right of the screen to enable)

> **[A-Frame: Compass | 8th Wall Playground | 8th Wall](https://www.8thwall.com/playground/compass-aframe)**
>
> This sample project demonstrates how to access compass data and use it on a 2D element and 3D entity.

---

<div class="post-metadata">

**Author:** ![James\_Kane](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@James\_Kane](https://forum.8thwall.com/u/James_Kane)\
**Post date:** [July 11, 2024, 2:31pm UTC](https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028/3 "2024-07-11T14:31:52Z")

</div>

Got it, that is exactly what I needed to know - did not realize iOS required a separate permissions check. Thank you, @TonyT!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/x8thwall/original/2X/9/9212a857458f1b03a6accb129e0f8cbea408e3e5.png) [@system](https://forum.8thwall.com/u/system)\
**Post date:** [July 15, 2024, 2:32pm UTC](https://forum.8thwall.com/t/device-orientation-accuracy-in-lightship-maps-implementation/2028/4 "2024-07-15T14:32:03Z")

</div>

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.