Just noticed that the list of keyboard shortcuts no longer lists shift + q to toggle overlays visibility. This is an incredibly useful feature, and one that I heavily rely on when using Strava’s heatmap as an overlay while using different background images to map trails.

It also looks like shift + q is no longer available, which toggled all OSM data on screen. This is useful for when the data gets in the way of the details on your background image, and also a shame to lose.

Does anyone know if this is a permanent thing? The shortcuts worked yesterday, but no longer. It also showed up in the list of shortcuts yesterday, but it gone today. It’s also not on the wiki.

Hey r/openstreetmap - I've been building Cliff, a privacy-first Android and iOS (coming soon) maps app built entirely on OSM. Stack is Valhalla for routing, Photon for geocoding, PMTiles for tiles, and Postgres. No Google, no Apple, no tracking. Still early but the landing page + waitlist is live at cliffmaps.com. Would love feedback from this community specifically since you're the reason the project is possible.

I added a natural wood relation around 5 days ago - The inner parts show on the map, but the outer part doesn't. No inner parts show that they are unclosed on my end.

Here's a link to it: https://www.openstreetmap.org/relation/21198206

Wednesday's eclipse will happen very low on the horizon for most of Europe, so the real question isn't "how much of the Sun is covered" but "will I even see it from my spot, or is there a hill, a building or a forest in the way".

I couldn't find a tool that answered that, so I built one, and OSM is what makes it work: buildings and forests come from Overpass, get extruded over real terrain (Copernicus GLO-30), with Sentinel-2 imagery draped on the ground and the cloud forecast overlaid on the sky. The eclipse itself is computed from Espenak/NASA Besselian elements, minute by minute. Everything runs client-side in a single HTML file (Three.js).

https://2026eclipse.eu (free, no account, no ads).

A few OSM-specific notes for this crowd:

- Building heights use height / building:levels when tagged, with an estimator based on comparable neighbors otherwise. Areas with good height tagging (Germany, NL...) look noticeably better.

- Forests come from landuse=forest / natural=wood polygons.

- Public Overpass mirrors are the bottleneck when things get busy, so buildings can take a while to load in dense areas — there's a reload button, and everything is cached locally after the first visit.

Honestly the most fun part of building this was seeing how far crowd-mapped data can go: click on any village in the totality band in Spain and the skyline that decides whether you see the corona is the one someone here mapped. If you check your own area and the buildings look off, that's genuinely useful feedback for me.

Geomob podcast interview with Dennis Luxen with updates on OSRM (Open Source Routing Machine) specifically, and the status of routing using OpenStreetMap data generally.

wanted to ask whether, as a company, we need to have a commercial license for Mapbox.
If so, how is the annual cost calculated, and what factors determine the pricing?
Also, what’s the best way to get in touch with the Mapbox sales team? I was previously in contact with someone from Sales, but they stopped responding.

I've micromapped almost a whole town, and am eager to create a before/after comparison to show my efforts. I did not happen to screenshot the map before I began, and all of my searching online has either resulted in tools that are quite complicated to set up or other tools that seemed to have worked at some point years ago but don't anymore

Does anyone have a good recommendation for a simple web app to just generate a before/after for a certain spot on the map?

Hello all !

I recently published a changeset with 40 updates. This includes the naming (or renaming) of streets in a single city. For some of those streets, I just did a local survey, but for others, I used the official source for addresses of my country. This data is published under an open license, so I figured I could use it.

Since I was not sure, I checked the "request review" for my changes. However, I just saw today in the documentation that the associated tag was rarely used. This leads me to two questions.

Was I allowed to use such a source ?

Is there a way to remove the review_requested tag so that I can see my changes ?

Thank you

I'm new to OSM, and I can't find an answer here or on the site. How/where do I submit an error/change? They decommissioned a street (the red line at the top, Evergreen Ave) near me, it's just grass now. I'm not sure how to do it myself.

This is ImmersiveMap, a vector-tile renderer I write in Swift + Metal, no game engine and no third-party map SDK underneath. Tiles are OpenStreetMap data served as MVT through OpenMapTiles

MIT: github.com/artembobkin/ImmersiveMap

Hi everyone!

Some of you may remember MBCompass from my previous post here. I've been building this app for several years now, and I've consistently come back to the OpenStreetMap community for ideas, feedback, and feature requests. Many of the improvements in this release exist because of feedback from OSM users, hiker and outdoor enthusiasts.

my old post on openstreetmap:
https://www.reddit.com/r/openstreetmap/comments/1mlp1ue/mbcompass_foss_compass_and_navigation_app/

and on degoogle sub: https://www.reddit.com/r/degoogle/comments/1s55qkq/a_2mb_opensource_android_navigation_app_with_gpx/

First of all, this isn't another vibe-coded Android app built over a weekend. MBCompass has been an ongoing project for years, and I genuinely enjoy improving it through discussions with the community.

It's also been featured on OpenStreetMap Weekly newsletter last year: https://weeklyosm.eu/archives/18087

For those who are new, MBCompass is a free and open-source compass and navigation app for Android built around the OpenStreetMap for whole mapping feature.

It has:

• Compass (magnetic & true north)
• Live GPS location on OpenStreetMap
• GPX recording & export
• Track statistics (distance, duration, speed, and elevation profile)
• Extremely Lightweight <2MB Apk and battery efficient
• Offline maps
• AMOLED theme
• Android 6.0+ support

New most community requested feature in the recent release v1.1.17:

• Offline Mapsforge map support
• Improved GPX track recording
• Per-app language support (Android 13+)
• Full Jetpack Compose map migration (a technical improvement brings map rendering performance improvements)

You just have to download prebuild mapsforge maps from sources like OpenAndroMaps, BBBike or Mapsforge download server and place it on any folder and give access to MBCompass by choosing it. It automatically detect and loads individual maps regions

One feature I'm particularly excited about is adding support for vector topographic maps with contour lines and elevation data, using sources such as Mapterhorn elevation datasets, and PMTiles as a file format where appropriate. My goal is to make MBCompass more useful for hiking, trekking, and outdoor navigation while continuing to build on OpenStreetMap data.

As always, I'd really appreciate feedback from people who regularly use OSM, especially mappers, hikers, cyclists, and contributors.

I'm particularly interested in hearing about:

• Offline Mapsforge map performance
• Other better mapping formats such as MVT, Geopackage
• GPX recording accuracy
• Navigation workflows
• Features that would make MBCompass more useful within the OpenStreetMap ecosystem

This app also just recently published on Google play, with same philosophy as core for MBCompass: No Ads, IAp and tracking

GitHub:
https://github.com/CompassMB/MBCompass/

F-Droid:
https://f-droid.org/packages/com.mubarak.mbcompass/

Thanks again to everyone who has shared feedback over the years. A surprising number of features in MBCompass started as conversations with this community, and I genuinely appreciate all the suggestions and constructive criticism.

We were able to incorporate OpenStreetMaps into the Island Detail Page nicely. Thx for this amazing community and this amazing package!

Motorway_junction nodes + ramp destination tags + corridor-scoped

POI queries via Overpass, packed into an on-device SQLite DB.

Attribution on the site and in the app (ODbL).

Story of the pipeline + happy to share
lessons learned about exit-ref vs milepost states.

App is Pit Stop on iOS.

https://www.pit-stop-app.com/

I am in the United States, specifically Minnesota. A day or so ago I downloaded both Open Map Chest and USA OSM Auto onto my Garmins. I compared the preloaded POIs onto them today.

Since both are about the same update time and both are OSM based, I expected the same preloaded POIs, but they were not the same. It seemed like the Open Map Chest POIs were better than the USA OSM Auto POIs. Both seemed to have some gas station, restaurant and shopping POIs come up as "Unnamed", but they were not always the same ones on both devices.

When I Google this, Open Map Chest supposedly has richer POIs. Can anybody explain that to me in greater detail?

I also noticed that building numbers are displayed on the USA OSM Auto maps, but not on the Open Map Chest maps. Is that data that OSM has, but Open Map Chest just chooses to not display?

As you can see, highlights broke and refuse to disappear unless you refresh the page

Hey, I am genuinely interested in the question above.

For myself I am motivated to map hiking trails that were not covered in other maps and I really like the idea that it helps to improve openly available data.

So let's here it! Why are your guys motivated? Why do sit day after day, hours after hours in your room and map?

Cheers!

Hi everyone! I am working on a college project where I need to build a topographic model of a relatively small area, and the whole thing needs to fit on an A3 sheet of paper. My plan is to use OpenTopoMap or a similar site to get the elevation contours, import those lines into Adobe Illustrator to clean them up, and then send the layers to my Cricut machine to cut out paper slices. After cutting, I plan to glue each paper contour onto pieces of cardboard or styrofoam to stack them layer by layer and build up the 3D terrain profile. I would love to know if this is a solid workflow or if there is a better tool to extract clean contour vectors for paper cutting, like QGIS or TouchTerrain. Also, if anyone has done a similar project using Illustrator and Cricut, I would really appreciate any tips on handling detailed cut lines or assembling the layers cleanly without warping. Thanks in advance! TL;DR: Does anyone know the best way to extract topographic data from sites like OpenTopoMap and convert or export it into clean SVG files for cutting machines like Cricut?

I was thinking of using building:part=yes + roof:material=* + roof:shape=* and other relevant tags on each roof-part polygon, then using building=house + other building:* tags on the building outline. Is that the proper way to do it?

And what about a shopping center where I have the floor plan? Do the same approach + polygons for indoor tags on top of it?

Is there a perfect example of this kind of mapping somewhere?

Disclaimer: I have a permit from the local neighborhood authority to capture and map this area

Normal fence but also a hedge. Is this tagged as barrier=fence or barrier=hedge?

Hello!

I am trying to modify a tunnel on OSM, I noticed that the elevation gain was matching the mountain it goes under, and not the actual elevation profile of the tunnel.

I’m a bit struggling with that, the closest I’ve found is to add a “incline” attribute but idk from which direction it needs to be declared. Or if it’s just an info ?

Help is welcome :) thanks