# Announcing Mapillary Camera Grant Program 3.0

**URL:** <https://forum.mapillary.com/t/announcing-mapillary-camera-grant-program-3-0/10509>\
**Category:** Community\
**Created:** [June 26, 2026, 9:32am UTC](https://forum.mapillary.com/t/announcing-mapillary-camera-grant-program-3-0/10509 "2026-06-26T09:32:35Z")\
**Posts on this page:** 1\
**Showing post:** 69

<div class="post-metadata">

**Author:** ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)\
**Post date:** [September 4, 2026, 4:26pm UTC](https://forum.mapillary.com/t/announcing-mapillary-camera-grant-program-3-0/10509/69 "2026-09-04T16:26:37Z")

</div>

> [@Lowiekse](#):
>
> I have Horizon Lock enabled.

@boris ~~I recommend leaving this function off for MAX(2) cameras due to this function’s significant image quality penalty~~, and I suggest adding this note to the Mapillary Help article. 3D reconstruction already provides Mapillary with computed camera poses, which can be used by MapillaryJS to display all images (not just 360° ones) level with the horizon. Hence, there is no need for source digital horizon leveling rasterization; MapillaryJS _just_ needs an update to make use of computed camera poses.

---

_[View the full topic](https://forum.mapillary.com/t/announcing-mapillary-camera-grant-program-3-0/10509)._
