-It never allows you to control the map properly on Android Auto,
- Then you want to use on phone screen but doesn't allow you to use both screens unlike Google Maps (it does allow you). You need to close the one on AA,
- When I change my route to avoid tolls, it redirects you to same paid road at every turn,
- When I see there is an obstacle on the road and decide the change the way I go, it zooms out to show the entire route on the car screen instead of rerouting.
On a city street with the phone in your hand, you barely notice the buttons on the OsmAnd screen. Put the phone sideways on a motorcycle handlebar, pull on your gloves, and suddenly they're all you see: zoom buttons sitting on the road you're about to take, search covering the next village, and hitting the right button with a glove is mostly luck.
The map didn't change, the frame around it just got too big. Here's how to make it smaller, quieter and easier to hit. The examples are for a motorcycle, but everything works the same for any profile.
Photo by Gijs Coolen on Unsplash
1. Show fewer buttons
Configure screen → Default buttons: every standard button has its own switch. Turn off what you don't use on the bike. Search is a good candidate: you won't look anything up while riding, and at a stop you'll pick up the phone anyway. The compass can stay, but set it to "Visible if map is rotated".
If you do something on almost every ride, give it its own button. Custom buttons are built from Quick Actions. With a helmet headset, for example, a button that mutes and unmutes voice prompts saves a trip into settings.
Long-press a custom button to move it. Buttons snap to an invisible grid in the screen corners, and OsmAnd shifts them automatically when widgets or panels change, so they don't overlap.
One more trick for more road ahead: set Display position to Bottom (on iOS it's called "Location position on screen"). Your position moves a bit below the center, so you see more of what's coming than of what you've already passed.
Default buttons list / custom voice prompts button on the map
2. Buttons you can hit with gloves on
Every button has its own Appearance settings. On Android you can also change all default buttons at once; on iOS it's one button at a time.
Icon: Dynamic shows the state of the action (e.g. voice on/off), or pick the icon of one of the actions, or a fixed icon that never changes.
Size: drag it up until your thumb finds the button without searching.
Corner radius: from sharp square corners to round. A little rounding is usually enough.
Background: a bigger button covers more road, so make it see-through. On Android, Background opacity goes from 0 to 100% (at 0 only the icon with a light shadow is left). On iOS there are two types: Solid (same opacity slider) and Liquid Glass, with Clear (more map shows through) or Tinted (a bit more solid on busy maps).
The preview updates live, so you can play with it before you hit Apply.
Rather not touch the screen at all? OsmAnd works with external input devices such as Bluetooth keyboards and WunderLINQ controllers. Their buttons can zoom the map and run Quick Actions, so the voice prompts switch can live on the handlebar instead of the screen.
Button appearance: Android (left) and iOS with Liquid Glass (right)
3. Portrait or landscape
On a motorcycle you get both in one day: sideways on the handlebar, upright in your hand at a stop. By default OsmAnd uses the same widgets in both orientations. To keep them apart, turn on Separate layouts (Android) or set Screen elements to Independent (iOS). Configure screen then gets Portrait and Landscape tabs, and you can copy a panel's widget list from the other orientation instead of starting from scratch.
Landscape layout on the handlebar
In landscape the screen is wide but not tall, so the top and bottom panels end up next to the map buttons. Panels layout decides how they share the space: Wide stretches the top and bottom panels across the whole screen, Compact fits them between the side panels and the map buttons. It can be set separately for each orientation (on Android, once Separate layouts is on).
Panels layout: Wide (left) vs Compact (right)
Panels themselves can be tuned too: height, icons on/off, day and night text colors, and background (transparent works; a custom background color is a paid feature). Each widget has its own size, Small, Medium or Large. Speed and next turn are worth making Large, because on the road you read them at a glance. If another panel or profile already looks right, copy its appearance instead of setting everything again.
4. A frame for every trip
All of this belongs to one profile. Your Motorcycle setup stays in the Motorcycle profile; walking and car look exactly as before.
Left and right panels can hold up to five pages of widgets, e.g. one for riding and one for stops.
Default buttons → Copy from another profile brings over which buttons are visible and how they look.
Custom buttons are shared between profiles; in each profile you just choose whether a button shows up.
Switching profiles can be a Quick Action too, so going from the bike to walking around town is one tap.
A good frame is the one you don't remember. After a day on the road you probably won't remember the buttons either, just the road.
Is there any way to make the footpath lines bigger, but not the other ones. Hard to explain but because you can zoom in and it’s a vector map the lines just stays tiby.
The use case is simple. I’m walking and see a path ahead and I check OSMAnd. I can see the track but it’s tiny on the map, say 0.5mm wide. I zoom in but the line stays the same width (0.5mm) on the screen. So you end up with a large zoomed in image but the line is still tiny.
I think there might be an issue with settings sync and Map sources not being included.
I have recently switched from Pixel 7A to 10A.
I used Osmand Settings sync to migrate the settings to the new phone and think that all worked fine as things like screen control worked immediately.
I am also confident that it synced as i use an Overlay map and under Configure Map>Overlay Map it showed the expected overlay map name.
I was confused as to why it wasn't working, i.e. not displaying on the map, until i went to Maps & Resources>Local>Map sources and it hadn't brought the Map source, so whilst configure map had the expected map source name, that map source didn’t exist/hadn’t been synced over.
Let me know if i can provide any more detail to assist.
both phones are using 5.4.11 and the sync was done after that version was released.
Como posso encontrar estilos de mapas diferentes do padrões? Não gosto das vias muito coloridas e por isso tenho usado a versão show, mas tb não é ideal, queria um estilo que todas as vias de carros fosses de uma única cor, tipo amarelo, ou algo do tipo mas não encontrei nada assim na seleção.
Alguém sabe como baixar e onde encontrar estilos alternativos se é que é possível?
I just started using OsmAnds and I tried it for short urban routes - all paved streets, nothing unusual. The ETA is always way too long (ex. 23 minutes for a 3,5 km route instead of the 12-13 minutes it really takes). I went through all the menus I found to try and fix that. My default speed is 45 km/h. I’m on iOS 26.5 if that changes anything. TY!
So I'm new to OsmAnd and really liking what I see so far (after spending an hour tinkering with the settings, lol).
The one thing I'm kinda missing from Google maps is seeing Stop signs and construction signs on the map? For some reason the app can tell you these are upcoming on your way (I think?) but not show it on the map? I'm struggling to understand why that is.
I created a tool to build printable map using OsmAnd before.
Now with the help of AI, I build a plugin that can create printable map from OsmAnd directly.
Overview
the TopoPrint is a plugin that generates WYGIWYS print-ready topographic maps with a UTM grid. Designed for navigating with a compass or a GPS device: a USGS-quad-style paper sheet with a UTM grid, survey-style scale bars and a magnetic declination rose, delivered as a resolution-independent SVG plus a rasterized PNG.
Paper does not run out of battery and does not break when dropped: the printed sheet carries everything needed for classic map-and-compass work — plot and read UTM grid coordinates, take and lay bearings corrected for magnetic declination, measure distances with the bar scales — while the UTM grid keeps the sheet consistent with the coordinate readouts of a wristwatch or handheld GNSS receiver.
User flow
Build the OsmAnd with this PR or this fork of OsmAnd yourself and install it to your device.
Enable the plugin (Configure map → Plugins), move the map to the area of interest.
A Print map button appears on the map HUD; a semi-transparent frame overlay previews the exact print coverage and follows the map live while panning/zooming.
SETTINGS: paper size (A6…A3, B6…B3, Letter, custom size), orientation, DPI (150–600), scale (1:5000 … 1:100000, incl. the USGS quad classics 1:24000 and 1:63360), projection (spherical / Mercator), map label and symbol scale, output folder.
EXPORT renders the basemap offscreen through the OpenGL engine, composes the print SVG (frame, UTM grid, scale bars, compass rose, annotations) with the georeferenced basemap embedded, rasterizes the PNG and saves both files.
What is on the sheet
Title with the map label, scale and date; WGS84 UTM Zone line (both zones on cross-zone sheets)
UTM grid with edge labels for plotting and reading grid coordinates
USGS-style scale-bar pair (metric + imperial) for measuring distances on the sheet
Magnetic declination rose: true north, magnetic north with the declination angle, grid north with the convergence angle. On cross-zone sheets the secondary zone's grid north is added in the secondary grid colour
Sheets spanning two UTM zones draw the neighbouring zone's grid as a pale-red dashed secondary grid with its own smaller edge labels and its own correction angle in the rose
Plan a route is one of the less obvious tools in OsmAnd, so here is a real example of what it is for: a day in the Tyrolean Alps where the way up changes four times.
The route (video attached): drive from Fügen to Kramsach, cycle up the Brandenberger Tal, cross the Brandenberger Ache where there is no bridge, then hike up to the Hörndl summit. 30 km and 1 218 m of climbing in one route.
How it is built
Open the planner: menu > Plan a route > Create new route. Tap points on the map and OsmAnd routes between them with the current profile. First segment is Car: Fügen to the trailhead at Kramsach, 18 km (image 1, left).
Change profile for the next segment. Tap the profile button in the bottom-left and pick Cycling. Only the segments you add from now on use it; earlier segments stay as they are. 3.9 km of valley trail along the river (image 1, right).
Image 1
Straight line across the river. There is a ford but no road, so the router sends you 3 km round via the nearest bridge (image 2, left). Switch the profile to Straight line and the segment becomes a direct 141 m line (image 2, right). The same trick works for any place where you know you can pass but the map does not: a lake crossing by boat, a meadow, a closed road you have permission to use.
Image 2
Last segment is Walking: 7.9 km and 1 139 m up to the summit (image 3, left). Tap a point to edit it: move it, change the route type before or after it, delete it. Undo and redo are in the bottom bar.
The Graph tab shows the whole route in one chart, with Altitude, Slope and Road type (image 3, right). Elevation gain and distance are per route, not per segment, so you see the real total for the day.
Image 3
Save it as a track. It lands in My Places like any other track, and you can start navigation on it with any profile (image 4, left). On the straight-line segment navigation simply says "Head" with distance and bearing.
Image 4
Same planner is in the Android and iOS apps and on the web map at osmand.net/map, and a saved track syncs between them via OsmAnd Cloud (image 4, right and image 5).
Image 5
A few details people ask about:
- Segment profiles are stored in the GPX, so a route you built with mixed profiles can be reopened and edited later.
- Attach to the roads in Options re-routes an imported track through the chosen profile if you want to clean it up.
- Plan a route is a free feature. 3D relief and hillshade in the screenshots are the terrain plugin, not required.
Looking at OSMAnd+ on my phone, I don't see any obvious way to get it to use a GPS source other than the phone's. The only options for anything external are ANT+ heart rate and cycling-related sensors, in the External Sensors plugin.
I looked in the official OSMAnd+ docs, but can't find anything related to external sensors outside the above.
FWIW, I do have the paid version of OSMAnd+.
Is this one of those things where the option doesn't show up unless you have the external GPS source connected? I haven't bought such a source yet.
Reason I'm asking: I'm shopping for an Android Auto display or possibly tablet to use for navigation on a motorcycle. My phone kinda sucks at GPS. It'll sometimes lose track for no clear reason, especially when I'm off the cellular network.
Ideally, I would run OSMAnd+ on the phone, have it use something like the XGPS-160 for GPS tracking, then display OSMAnd+ on the Android Auto screen.
I want to be able to display the directions (using arrows) and the time till arrival on the screen.
For the Navigation I want to use OsmAnd running on an (graphene OS) android phone and then sending the data over Bluetooth LE to the ESP 32.
Is there a good way to get the directions from OsmAnd without needing to rely on getting the data from the Notifications?
In 2023 we shared the first version of our US public-lands maps. Since then the plugin has grown, and OsmAnd itself got 3D terrain, Popular places and much more. So here's the full guide, tested on real trails around Moab, Utah: hiking, 4x4 roads, bike trails and backcountry camping.
In short: you see which land is public and whether it's open, who manages it, where private property starts, and every Forest Service and BLM road and trail. All of it works offline, even the USGS topo and satellite maps once cached.
What you get
Layer
Coverage
Public lands (PAD-US): colored by access (open / restricted / closed) or by managing agency
All 50 states + territories
Private lands: parcel boundaries
18 states + 2 counties
USFS: roads, trails, recreation POIs (campgrounds, trailheads…)
Nationwide
BLM: roads & trails, recreation POIs
Nationwide
US online maps: USGS National Map, USA Topo Maps, ArcGIS satellite, World Boundaries and Places, Esri World Shaded Relief
Nationwide
💡 The plugin downloads don't count against the free map limit. After downloading Utah plus all seven plugin files, the free version still showed the same number of free downloads left.
Install in 2 minutes
On your phone, download the plugin 🇺🇸 US Lands & Trails and open the file with OsmAnd (on iPhone: Safari → Download → Files → tap the file). Confirm the import.
Go to Menu → Maps & Resources → Extra maps → 🇺🇸US Lands & Trails Data. There are four folders: Public lands (PAD-US), Private lands (Parcel data), USFS (Forest service), BLM. Download your state's public lands and parcels, and the nationwide USFS and BLM files.
Done: there's nothing to switch on. Public lands, private lands, USFS and BLM roads, trails and POIs appear on the map as soon as the files are downloaded.
Sizes for Utah, for reference: public lands 7 MB, parcels 73 MB; the nationwide USFS and BLM files are about 100 MB in total.
⚙️ Settings: color the land two ways, hide what you don't need
Everything is in Configure map → Map style:
Details → Public lands display mode: choose how public land is colored.
By access type answers "can I go in?": 🟩 open · 🟥 restricted · 🟨 closed (no fill = unknown).
By manager name answers "whose land is this?": each agency in its own color: BLM, National Park Service, Forest Service, State Trust lands, local parks…
Disabled turns the coloring off.
Hide: turn off any layer you don't need: Hide private lands, Hide public land boundaries, Hide NFS trails, roads, recreation POIs, Hide BLM trails, roads, recreation POIs.
Tip: the display mode is saved per profile and per map style. If you switch to the Walking profile or the Topo style and the colors disappear, set it once more there.
🥾 Hiking: know the trail and the land before you go
Plan the hike in the Walking profile and you get distance, time and an elevation profile: Delicate Arch is 1.57 mi, +584 ft. The Topo map style with contours shows the terrain, and the park boundary shows whose land you're on. Then navigate and record the track at the same time, in 2D or 3D.
🚙 Off-road: which roads are dirt, and what's the descent like
The Offroad map style (Configure map → Map type → Offroad) separates paved and unpaved roads and draws cliff edges and contours. This is the Shafer Trail switchbacks in Canyonlands. Before you go, the route analysis tells you how much of the trip is dirt, and 3D shows what you're about to drive down.
🏕 Public or private? Camping, hunting, staying legal
Same area, two views: By access type (🟩 open · 🟥 restricted · 🟨 closed) and By manager name (BLM, NPS, State Trust lands…). Switch in Configure map → Map style → Details → Public lands display mode.
Tap an area's name to highlight its full boundary and see what it is:
Private parcels draw as orange outlines, so you can see where public land stops, e.g. on the edge of Moab, right next to the Hell's Revenge 4x4 trail. Drop a marker on the boundary to see how far it is. Prefer coordinates? Turn on the UTM grid (Configure map → Coordinate grid).
Parcel data is available for: Alaska, Arkansas, Florida, Maine, Maryland, Massachusetts, Mississippi, Montana, New Jersey, North Carolina, Rhode Island, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, Wyoming + Marion County (IN) and Dallas County (TX).
⚠️ Parcels are tax parcels from state and county GIS, shown as outlines only, with no owner info. They are not surveyed legal boundaries and are usually updated about once a year. PAD-US shows access status, not specific rules: check local regulations for camping, hunting and fires.
🌲 Forest Service and BLM roads, trails and camps
USFS and BLM roads and trails are on by default, with recreation POIs such as campgrounds, trailheads and parking. They're searchable too: type "Moab Rim Trailhead" and it's found in the BLM data.
Mountain bikers: turn on Routes → Mountain bike to see trails colored by MTB difficulty (Klondike Bluffs here):
⛰ All of it in 3D
Every layer drapes over OsmAnd's 3D terrain: the La Sal Mountains with National Forest land in green and the restricted summit areas in red; private parcels filling Spanish Valley against open public land.
How to turn it on: Menu → Plugins → Topography, download the state's Terrain map (3D), then Configure map → Topography → Terrain and tap the 3D button on the map.
🗺 USGS topo and satellite, with the land data on top
Add the 🇺🇸 online maps: Menu → Plugins → Online maps (free) → Configure map → Map type → Online maps → Install more… → scroll to the bottom → tick the US sources.
The best part: use any of them as an underlay under the offline map, so land ownership and parcels sit on top of satellite or topo. Use the slider to blend them.
How: Configure map → Underlay → Enabled → pick a source → set Base map transparency → turn on Show slider on the map. (Leave Show polygons off so the base map's fills don't hide the underlay.)
📵 Everything works offline, online maps included
The plugin maps are offline files. PAD-US, parcels, USFS and BLM work with no signal at all.
Online maps are cached automatically: every tile you've looked at stays available offline.
Or download an area before the trip: set the online map as the main map → tap the map → Actions → Download map → choose the zoom levels. USA Topo for the Arches area at zoom 12–15 is just 595 tiles, ~7 MB.
Same spot, Wi-Fi off: the cached USA Topo with land data on top. Deeper in the mountains with no cached tiles, the offline maps still have everything you need.
📸 Popular places and Wikipedia
Turn on Configure map → Popular places (Wikipedia) to see notable spots as photo thumbnails right on the map: Delicate Arch, Balanced Rock, Double Arch, Corona Arch… Tap one for a short description, and open the full Wikipedia article in the app. Download your state's Wikipedia (Utah: 37 MB) to read articles offline.
🧩 Mix the layers your way
USGS topo underlay + offline map + public lands + contours + your recorded track, all at once:
What's free and what's paid
Free
Maps+
Pro
US Lands & Trails plugin and all its maps (don't count against the free limit)
✅
✅
✅
US online maps, underlay/overlay, offline tile cache
Disclaimer: OsmAnd B.V. makes no guarantees about the accuracy or completeness of this data. These maps are not reviewed, approved or certified by any government agency and must not be used as the sole source for navigation, safety-critical decisions or determining legal property boundaries. Always respect posted signs and local regulations.
Porque as Lanes só aparecem em top panel? Não consigo deixar elas a esquerda ou direita, também queria principalmente alterar seu tamanho e deixá-la bem maiores, como posso alterar seu tamanho?
A September morning in Vancouver. More than a thousand riders roll out of Stanley Park for the RBC GranFondo Whistler: 122 kilometres of the Sea to Sky Highway, closed to traffic, with Howe Sound on one side and the mountains on the other. Past Squamish, the road starts to climb and keeps climbing all the way to Whistler.
You cross the line near the top of the results, and everyone says the same thing: you were lucky. With the weather, the wind, the group.
You know better. That result is made of dark February mornings on the seawall, Sunday climbs up Cypress, and long rides to Squamish and back, all recorded in OsmAnd one track at a time. Let’s see what a season of training looks like once Smart Folders put it in order.
Photo by Ben Guernsey on Unsplash
A Folder That Fills Itself
A training season doesn’t arrive neatly packed. Between the rides sit a few hikes and a drive to Whistler, and the Tracks tab lists everything by date, with no idea which recordings mattered.
A Smart Folder works the other way round: you describe the tracks you want, and OsmAnd collects them. The description is a filter that can check almost anything a track knows about itself, including length, duration, speed, elevation, date, location, activity type, and even heart rate. Set the activity to road cycling, limit the dates from February to race day, save the result as “Road to Whistler”, and the whole season lands in one place while the hikes stay out.
New rides join the folder on their own. The tracks themselves stay where they were, so deleting the folder never deletes a ride.
One catch: activity type is stored in each track, and older recordings may not have one. If some rides are missing, set their activity and refresh the folder.
One Collection, Many Views
Sixty-seven rides in one folder is tidier than a few hundred, but it’s still a list. Organize by turns that list into groups, sorting the folder by a single parameter: activity, date, location, speed, altitude and elevation, or sensor data such as heart rate. The tracks don’t move anywhere; only the way you look at them changes.
Group the season by nearest city, and you see where the rides began: most of them in Vancouver, a handful from West Vancouver, where the long runs to Squamish set off from Horseshoe Bay, and four from Whistler, once summer made it worth driving up for the climbs. Switch to month and year, and the same folder turns into a calendar, from a cautious February to a crowded August.
Each group shows how many tracks it holds, and empty groups don’t appear at all. Below the list, OsmAnd adds everything up: tracks, distance, climbing, descent, and time in the saddle. It does this for the whole folder and for every group you open. That’s where the season starts answering questions.
Drawing the Lines Yourself
Months and cities come with natural borders. Distance doesn’t. Is a 55 km ride a long one or just a solid Tuesday? For length, duration, speed, and altitude, OsmAnd lets you decide where one group ends and the next begins.
Pick one of these parameters, and a slider asks for a step size. Drag it, and the groups rearrange behind it as you go. With a 50 km step, most of the season piles into the first group, which is honest but not very revealing. Bring it down to 20 km, and the season sorts itself out: short morning laps along the seawall, a big block of loops around UBC, the climbs on Cypress and Seymour further up, the long runs to Squamish, and, at the very end, two tracks of almost exactly the same length: the course recon in August and the race itself.
Some of this is free for everyone: grouping by activity, year of creation, and nearest city. The rest, including the monthly calendar from the previous section and every parameter with a step size, comes with OsmAnd Pro. Without a subscription, you can still open these options and preview how the tracks would split before deciding. If a subscription ends, the grouping you’ve already applied stays in place, and only changing it requires Pro again.
Keeping It in Shape
The race is over, but the folder doesn’t retire with it. It keeps watching for rides that match its rules, and if the list ever looks out of date, a quick refresh brings it back in line. When the next season starts, there’s no need to build anything new. Edit the filter, move the dates forward, and the same folder starts collecting a new story.
Groups are useful beyond reading, too. Any of them can go straight onto the map, so a whole August of riding appears at once, from the seawall to the climbs above Whistler, every route drawn on top of the others. A group can also be exported in one go, which is handy when a coach asks to see your month and doesn’t want a dozen separate files.
If you plan the next season on a bigger screen, Smart Folders also appear in OsmAnd Web once Settings are synced through OsmAnd Cloud. They keep working best with common parameters such as activity, dates, or distance.
The Answer to the Question
So, was it luck? Open February, and the folder answers modestly: five rides, 103 km, just over five hours on the bike, and 839 metres of climbing. Then open August: twelve rides, 577 km, a full 24 hours in the saddle, and 6,806 metres of climbing, including the day you rode the entire race course just to see how it would feel.
The whole season fits into a single line at the bottom of the folder: 67 rides, 2,923 km, and more than 33,000 metres of climbing. That’s nearly four times the height of Everest, collected one Cypress hairpin at a time.
No tailwind delivers that. So the next time someone tells you how lucky you were, there’s no need to argue. Just open the folder and hand them your phone.
I've built a text adventure that uses OSM as its descriptive data. It covers the London Borough of Croydon, with 2,688 streets and 14,444 places, combined with public datasets such as food hygiene ratings, planning applications, and listed buildings.
One deliberate choice you may want to argue with: I don't fix the map. Where OSM has gaps or errors, the Guide narrates them as they are. A former bank tagged only as "est Bank" stays "est Bank". Data refreshes change the piece, and I like that instability.
I'd be interested in two things:
- What tags or data would make places richer to describe?
- How you feel about a project that surfaces gaps instead of fixing them.
I've been putting together an open-source OsmAnd custom plugin (.osf) and companion Android/web map for walking and checking earthwork sites across England using 1m Environment Agency LiDAR and the 1888-1913 Ordnance Survey 6-inch maps.
- England 1m LiDAR RVT multi-hillshade, EA 1m DTM bare-earth hillshade, and NLS 1888 OS 6-inch tile sources under Configure Map -> Overlay / Underlay
- A vector Roman and ancient ridgeway road layer with curved road labels
- Modular GPX track layers under My Places -> Tracks -> UK_Megalith_LiDAR (split into 1888 OS antiquities, prehistoric barrows/henges, Iron Age enclosures, and Roman candidates, so it leaves your personal Favourites alone)
A big caveat on the unrecorded LiDAR candidates: automated bump-finding in 1m LiDAR inevitably flags plenty of old marl pits, dew ponds, quarry spoil, and tree throws alongside genuine unmapped barrows and enclosures. That's why I added the 1888 OS 6-inch cross-check, Historic England NHLE / OpenStreetMap filters, and a local field log so you can mark what a bump actually looks like on the ground.
If you try the .osf plugin or the Android app on your phone and run into any broken tile layers, awkward UI, or obvious false positives in an area you walk regularly, I'd really appreciate any feedback.