# Maps 2.0: Our biggest map layer update ever! (looking for feedback)

**URL:** <https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603>\
**Category:** Website\
**Created:** [August 6, 2026, 1:06pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603 "2026-08-06T13:06:38Z")\
**Posts on this page:** 20\
**Page:** 4

<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:31am UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/62 "2026-08-20T08:31:37Z")

</div>

Thanks, this is helpful.

PS Been there. At some point I wanted my dog to run by my side when I cycle (I’ve seen this a few times in the city), but it looks like my dog has other priorities immediately after I get on a bike ☹  
\_\_  
BR, Yaro

---

<div class="post-metadata">

**Author:** ![Anders](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/anders/32/55_2.png) [@Anders](https://forum.mapillary.com/u/Anders)\
**Post date:** [August 21, 2026, 3:24pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/63 "2026-08-21T15:24:14Z")

</div>

> [@GITNE](#):
>
> Good naming and consistency are crucial when building public facing software systems. For example, `map2` is not a particularly good name for a URL query component.

This has now been fixed.

`map2=true` is now `captures=all|best|needed` to denote which layer to use. Existing links will resolve to `captures=all`, and the default is `all` at the moment (`best` will be the default eventually though).

---

<div class="post-metadata">

**Author:** ![koninklijke](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@koninklijke](https://forum.mapillary.com/u/koninklijke)\
**Post date:** [August 31, 2026, 9:54pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/64 "2026-08-31T21:54:12Z")

</div>

> [@Yaro](#):
>
> Also, bicycles are usually the hardest to classify (just FYI).

Dear @yaro,

It is safe to assume that koninklijke and its trusty companion konink360 are helmet mounted, and that the helmet is worn for cycle rides, but bear in mind that the rider may occasionally have dismounted at say roadworks or to avoid recording themselves committing some traffic violation - which from 1 sep’26, in Belgium, apparently now is a traffic crime of a lower punishment category - unless the newspaper article about the new Penal Code had things the wrong way.

Best,

---

<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:** [September 7, 2026, 2:02pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/65 "2026-09-07T14:02:04Z")

</div>

Hi @Lowiekse, the sequence you’ve shared [here](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/59) are now on the map and matched to the roads, it looks like, correctly.

At the same time, some other sequences you’ve shared in other message are not on the map yet, but I will check them as well, just a bit later, and they will appear on the map 🙂  
\_\_  
BR, Yaro

---

<div class="post-metadata">

**Author:** ![Lowiekse](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/lowiekse/32/72164_2.png) [@Lowiekse](https://forum.mapillary.com/u/Lowiekse)\
**Post date:** [September 7, 2026, 2:06pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/66 "2026-09-07T14:06:52Z")

</div>

> [@Yaro](#):
>
> the sequence you’ve shared [here](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/59) is not on the map and matched

Hi @Yaro,

What exactly do you mean by this?

BR Louis

---

<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:** [September 7, 2026, 2:30pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/67 "2026-09-07T14:30:56Z")

</div>

Oh, that was a big typo on my side. The 3 sequences which you shared [here](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/59) were classified as vehicular and hence were excluded from the “best captures” layer (as the algorithm couldn’t match them to the neghbouring roads). I manually updated them to be “bicycle” and now the changes are on the map and the images from those sequences are contributing to the “best captures” layer.

PS updated the initial message as well

\_\_  
BR, Yaro

---

<div class="post-metadata">

**Author:** ![Lowiekse](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/lowiekse/32/72164_2.png) [@Lowiekse](https://forum.mapillary.com/u/Lowiekse)\
**Post date:** [September 7, 2026, 2:40pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/68 "2026-09-07T14:40:43Z")

</div>

Great, Yaro. Thank you. 🥳

---

<div class="post-metadata">

**Author:** ![Barro](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@Barro](https://forum.mapillary.com/u/Barro)\
**Post date:** [September 13, 2026, 9:13pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/69 "2026-09-13T21:13:43Z")

</div>

Looks like landuse=military is not filtered (example: [Relation: ‪Santahamina‬ (‪16521302‬) | OpenStreetMap](https://www.openstreetmap.org/relation/16521302/) → [https://www.mapillary.com/app/?lat=60.14532409631266&lng=25.04828371188694&z=13.742924269996776](https://www.mapillary.com/app/?lat=60.14532409631266&lng=25.04828371188694&z=13.742924269996776)) out from the captures needed layer.

---

<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 13, 2026, 10:27pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/70 "2026-09-13T22:27:38Z")

</div>

Mapillary’s interpretation here is correct because the `landuse` key **does not** denote legal or physical **access** , nor does `landuse=military` imply `access=no` or `access=private`. `landuse` denotes the **use of land** only, that is, how a land area is used or zoned. Furthermore, military land uses exist where public access is generally permitted and photography may or may not be allowed. Hence, if the area outlined by the relation you refer to is off limits for the public then the ways in that area should each be explicitly tagged with `access=no` or `access=private` (depending on context).

The same is true for `landuse=retail` areas, where usually most of the land is publicly accessible but some parts, like loading and unloading alleys, employee parking aisles, inner warehouses, or offices may be accessed by staff or personnel only (`access=private`).

---

<div class="post-metadata">

**Author:** ![Barro](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@Barro](https://forum.mapillary.com/u/Barro)\
**Post date:** [September 14, 2026, 7:03pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/71 "2026-09-14T19:03:53Z")

</div>

Mapillary has its own interpretation of various roads that it considers worthy for the “captures needed” highlights. It isn’t based on the legal interpretation if public access is allowed or not. Mapillary developers can filter out military areas with the principle of “better be safe than sorry” if they want to. 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/)

I’m just bringing this possibility into attention, as this layer looks weird when it is asking to go and photograph a local military garrison. Especially when it’s clearly visible from the default OpenStreetMap Carto layer that this is a restricted area, no matter how you would think it from a database perspective.

---

<div class="post-metadata">

**Author:** ![AmericanMapper](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/americanmapper/32/73539_2.png) [@AmericanMapper](https://forum.mapillary.com/u/AmericanMapper)\
**Post date:** [September 14, 2026, 7:47pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/72 "2026-09-14T19:47:06Z")

</div>

Its because OSM has a lot of wrong data on driveways also. Private drives with 20 “no trespassing” and “violators will be shot” signs may still show up as a capture needed. You can contribute on OSM to fix this but its A LOT of wrong info, and it would take forever just to fix all in your county/region.

---

<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 14, 2026, 10:07pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/73 "2026-09-14T22:07:56Z")

</div>

> [@AmericanMapper](#):
>
> Its because OSM has a lot of wrong data on driveways also.  
> You can contribute on OSM to fix this but its A LOT of wrong info, and it would take forever just to fix all in your county/region.

Do not confuse wrong data for lack of data or unmapped properties of existing data. Many ways in OSM have been imported from public sources or machine mapping, where simply some kind of `highway` tagged ways (often without names) had been imported to get started. Thus, OSM is not per se wrong but just incomplete or outdated, like every other map is too. And, I do not know about you but you might have noticed that Mapillary exists exactly for this reason. Mapillary exists to close this data gap in OSM where needed. If you see ways that lack `access=private` then do not complain. Fix the map (OSM database) so that everybody can benefit.

---

<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 14, 2026, 10:28pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/74 "2026-09-14T22:28:07Z")

</div>

> [@Barro](#):
>
> Mapillary developers can filter out military areas with the principle of “better be safe than sorry” if they want to.

They will not do it for the exact reasons I have explained. OSM tags have a meaning, you know.  
Mapillary has nothing to be sorry about because as always, contributors have to follow local laws and regulations. The [Mapillary Terms of Service](https://www.mapillary.com/terms) reiterate this. Do not confuse the visualization of a (potentially) incomplete dataset for incitement to break laws and regulations.

Besides, OpenStreetMap Carto does not render ways as private in `landuse=military` areas either and nobody complains that “the map says there is a public access road in a military installation but I am forbidden to go into a restricted zone”. It is the correct way to interpret the OSM data and render the map. The issue is neither with reality, the definition, nor interpretation of tags. The issue is that the map data is incomplete.

The best thing you can do is to simply fix the map, not the definition and interpretation of established tags.

---

<div class="post-metadata">

**Author:** ![AmericanMapper](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/americanmapper/32/73539_2.png) [@AmericanMapper](https://forum.mapillary.com/u/AmericanMapper)\
**Post date:** [September 14, 2026, 11:56pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/75 "2026-09-14T23:56:49Z")

</div>

I agree with both comments you left GITNE. I have gone and fixed some on OSM already in my local area, but again, its a lot. But hopefully other OSM contributors can also help, as this is a BIG issue with the new “captures needed” tag.

---

<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, 2:46am UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/76 "2026-09-15T02:46:34Z")

</div>

Great! 👍 Thanks to your contribution that huge heap of work just decreased a bit. Please, keep up the good work. Rome was not built in a day, either. 😉 Mapping is not a one time event nor ever finished, it is an ongoing collaborative process. Though eventually, map data can saturate over time to some extent locally.

---

<div class="post-metadata">

**Author:** ![Barro](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@Barro](https://forum.mapillary.com/u/Barro)\
**Post date:** [September 17, 2026, 8:58pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/77 "2026-09-17T20:58:46Z")

</div>

What you just wrote is actually in conflict with Mapillary’s own capture guide: [https://help.mapillary.com/hc/en-us/articles/115001477865-The-Complete-How-To-Guide-on-getting-great-Mapillary-imagery#01JE70ZTFNDTJ3QARH5WGXYX6W](https://help.mapillary.com/hc/en-us/articles/115001477865-The-Complete-How-To-Guide-on-getting-great-Mapillary-imagery#01JE70ZTFNDTJ3QARH5WGXYX6W)

> ## **Do NOT capture:**
> 
> - …
> - Military and other sensitive areas
> - …

So basically this “captures needed” layer is in conflict with Mapillary’s own capture guide if they are guiding people to such areas. No matter if it’s permissible or not.

---

<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:** [September 18, 2026, 8:18am UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/78 "2026-09-18T08:18:23Z")

</div>

Thank you for the report and for all the investigation @gitne @Barro @AmericanMapper regarding captures needed roads. I will create a task to double-check those findings. Specifically, I will check whether the same rules apply correctly for images (captured in the excluded areas) and for roads with “captures needed”.

\_\_  
BR, Yaro

---

<div class="post-metadata">

**Author:** ![ivanbranco](https://avatars.discourse-cdn.com/v4/letter/i/9e8a1a/32.png) [@ivanbranco](https://forum.mapillary.com/u/ivanbranco)\
**Post date:** [September 28, 2026, 10:32am UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/79 "2026-09-28T10:32:25Z")

</div>

I captured some imagery from roads without it. But in the map they are still rendered as “capture needed”. Other roads I captured and uploaded in the same day are fine tho. What could be the reason? I can send an example in private if needed.

---

<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:** [September 28, 2026, 12:19pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/80 "2026-09-28T12:19:52Z")

</div>

Thanks for the message. I would think the main reasons are either really bad GPS or sequence capture type misclassification (can be just an issue as well, of course). If you’re okay with it, just DM me the links to the sequences and I can check the reason.

\_\_  
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:** [October 6, 2026, 8:11pm UTC](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603/81 "2026-10-06T20:11:14Z")

</div>

The “Captures Needed” map layer looks to be overly selective about public `highway=service` ways, i.e. those that have no `access` tag. They are left out instead of being colored red when no imagery is available. Maybe it is due to lack of the `name` tag on many such public service roads? I do not know. I have not tested (because I do not want to mess around with the production OSM database) nor researched whether `access=yes` or `access=public` tagged public service roads get included by “Captures Needed”.

If it is not too much effort perhaps publishing a list of “Captures Needed” sensitive tags might help.

[Previous page](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603.md?page=3)

[Next page](https://forum.mapillary.com/t/maps-2-0-our-biggest-map-layer-update-ever-looking-for-feedback/10603.md?page=5)
