# “Captures Needed” in Restricted Zones

**URL:** <https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636>\
**Category:** Website\
**Created:** [August 20, 2026, 6:18am UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636 "2026-08-20T06:18:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmic](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/rmic/32/73523_2.png) [@rmic](https://forum.mapillary.com/u/rmic)\
**Post date:** [August 20, 2026, 6:18am UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636/1 "2026-08-20T06:18:02Z")

</div>

Hi everybody,

I’m often using the “Captures Needed” map to plan my capture routes. There are however a series of routes and paths that are marked in this red / salmon color, that are not publicly accessible, and still stay in red on the map.

I thought that fixing the “access” tag on OSM might help update the Mapillary map, but even a few weeks after the change, I don’t see any change on the mapillary map.

Is this wanted ? Should the mapillary map take these OSM access tag into account ? Is there any plan about that ? Do we expect the land owners or visitors to mapillarize private properties as well ?

 ![image](https://us1.discourse-cdn.com/flex015/uploads/mapillary/original/3X/5/2/5275ca530f561e187dc472b7776d87bd4a0b65b9.jpeg)

---

<div class="post-metadata">

**Author:** ![Yaro](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/yaro/32/71532_2.png) [@Yaro](https://forum.mapillary.com/u/Yaro)\
**Post date:** [August 20, 2026, 8:25am UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636/2 "2026-08-20T08:25:28Z")

</div>

Hi @rmic, thank you for the report. We are looking into it and will check the roads classification to identify the root cause. We have had similar reports, like [here](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/41).

\_\_  
BR, Yaro

---

<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:** [August 20, 2026, 10:37am UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636/3 "2026-08-20T10:37:44Z")

</div>

> [@rmic](#):
>
> I thought that fixing the “access” tag on OSM might help update the Mapillary map, but even a few weeks after the change, I don’t see any change on the mapillary map.

Adding access tags to OSM in such instances — after on the ground verification, of course — is the best thing you can do. So, thank you for doing it. 👍 Hence, please keep up the good work. Please also keep in mind though that mapping `access=private` is not always trivial due to many private road owners allowing delivery and emergency services on their roads. However, private roads are always off limits for capturing, of course.

The reason why you do not see updates on the Mapillary map layer yet is because Mapillary does not depend on OSM data directly any longer (especially due to business reasons). Mapillary uses [Overture Maps](https://overturemaps.org), a Meta driven map aggregator/distiller. And, although Overture Maps builds its dataset basically on the OSM road network, it has its own release cadence. Hence, Overture Maps ≠ OpenStreetMap, nor are their update cycles. Furthermore, the Mapillary coverage and image alignment layers have their own update cadence. So yes, OSM updates trickle down quite slowly but eventually everything will become updated nevertheless. And no, you cannot commit directly to Overture Maps.

> [@rmic](#):
>
> Is this wanted ? Should the mapillary map take these OSM access tag into account ?

Yes, please continue surveying, capturing such places for evidence, and updating OSM.

> [@rmic](#):
>
> Is there any plan about that ? Do we expect the land owners or visitors to mapillarize private properties as well ?

There is no plan. 😉 Everybody is free to commit or not to commit edits to OSM.

---

<div class="post-metadata">

**Author:** ![rmic](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/rmic/32/73523_2.png) [@rmic](https://forum.mapillary.com/u/rmic)\
**Post date:** [August 20, 2026, 11:23am UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636/4 "2026-08-20T11:23:58Z")

</div>

Thanks for your answers !

I’ll continue updating OSM (which I would have done anyways, but if it can help on both sides, it’s even better).

---

<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 15, 2026, 3:28pm UTC](https://forum.mapillary.com/t/captures-needed-in-restricted-zones/10636/5 "2026-09-15T15:28:32Z")

</div>

Just for the sake of topic clarity, I have moved the discussion to this topic.

> [@Maps 2.0: Our biggest map layer update ever! (looking for feedback)](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/71):
>
> Especially as exact tagging access restricted areas is always a bit up for debate: [Rajavyöhykkeen väylille access=no vai access=permit?! - Suomi (Finland) - OpenStreetMap Community Forum](https://community.openstreetmap.org/t/rajavyohykkeen-vaylille-access-no-vai-access-permit/146566/)

On the detail of `access=permit`, let’s read the description (or _definition_) first:

> **[When to use - Tag:access=permit - OpenStreetMap Wiki](https://wiki.openstreetmap.org/wiki/Tag:access%3Dpermit#When_to_use)**
>
> As originally proposed, this tag should be used in cases where a permit is required, but is routinely granted to everyone requesting it. In cases where access to permit is obstructed it would be more appropriate to tag these areas access=private or...

The description is pretty much clear to me. Then how should Mapillary interpret `access=permit` when rendering the “Captures Needed” map layer? Well, probably the same as `access=no` and `access=private` because even though `access=permit` may constitute a pretty low bar for someone seeking access, it nevertheless remains a bar and thus is no longer ordinary unrestricted public access. Furthermore, `access=permit` nor even `permit=*` say anything about whether photography or filming is allowed or not with a permit in the restricted zone or by whom. For that to know `access=permit` ways would need to be tagged additionally with something like `photography=yes` or `filming=yes`, which is something that probably goes way beyond what should be in the OSM database.
