Help
How to read the route line and the passes, what happens to your files, links and Garmin, and what we do with your data. How routing, settings, the heatmap, loops, riding time and the weather work, with all the numbers, is on How No Mapa works.
Colours and dashes on the line
The line shows two things at once: colour is the grade, pattern is the surface. The elevation profile repeats both.
Bikes (road, gravel, MTB): the colour changes with every 1% of grade, from blue downhill through green on the flat to yellow, orange and red uphill; 18% and steeper is black.
↓12%↓6%0↑6%↑12%↑18%
| Walking | |
|---|---|
| ↓ steeper than 30% | ↓ 10–30% |
| ±10%, easy | ↑ 10–20% |
| ↑ 20–30% | ↑ 30–45% |
| ↑ steeper than 45% |
| Surface | Pattern |
|---|---|
| Asphalt, concrete, paving | solid |
| Compacted, fine gravel, cobbles | long dashes |
| Gravel, dirt road | short dashes |
| Ground, trail | dots |
| Straight leg | grey dashes |
Surface comes from OpenStreetMap tags. Without a tag it is guessed from the road type, and the profile marks such parts as “no data”.
Straight legs
If the trail you need is missing from OpenStreetMap, switch the leg to a straight line: right-click the line, long-press on a phone, or press B over it; Shift+click on the map adds one straight leg, and B with the cursor away from the line draws all new legs straight. A straight leg is drawn as a grey dashed line; its elevation comes from an open terrain model.
Mountain passes
The “Passes” layer combines two sources:
- OpenStreetMap: about 37,000 passes worldwide, many with elevation, some with a grade.
- FSTR catalogue: the open pass classifier of the Russian Sport Tourism Federation, about 7,500 passes in the former USSR and neighbouring ranges. It has grades, terrain, what the pass connects and first crossings. Names and descriptions from it are in Russian.
When a pass is in both sources and the points are close, they are merged into one record, and the grade is taken from the FSTR catalogue. The pass card always tells where the data comes from.
Zoomed out, only graded passes are shown; closer in, named ones appear, and from zoom 12 all of them.
Grades
| Grade | What to expect |
|---|---|
| NC | Non-graded. A trail or a gentle grassy slope, no snow or ice. |
| 1A | Easy. Scree, grassy slopes, small snowfields. Sometimes an ice axe for self-belay. |
| 1B | Moderate. Steep scree and snow, short rock sections. Ice axe self-belay, a rope in places. |
| 2A | Intermediate. Snow, ice and rock, covered glaciers. Crampons, ropes, roped travel. |
| 2B | Difficult. Steep ice and rock, long rope work. Mountaineering skills required. |
| 3A | Very difficult. High altitude, steep ice and rock walls. |
| 3B | The hardest passes: technical climbing, high altitude, rockfall and avalanche danger. |
An asterisk after a grade (for example 1B*) marks a pass at the upper end of its grade.
Files and links
- Saving is automatic. Without an account, routes stay in this browser; with one, they sync to every device you sign in on.
- A short link stores a full copy of the route (line, checkpoints, notes) and opens it for anyone who has the link, with or without an account.
- Download GPX gives a GPX 1.1 track with elevation, and your checkpoints as waypoints with their names and notes. It has no timestamps and no turn instructions.
- Open GPX or KML, or drop the file on the map. A track can become an editable route: the planner rebuilds it along the roads, keeps the elevation or takes it from the terrain model, and reads surfaces from the map.
Send to Garmin (beta)
Garmin offers no public interface for other apps to put courses on your watch. No Mapa therefore uses the same sign-in as the Garmin Connect app, through the open-source library python-garminconnect. The course arrives in Garmin Connect and, if you choose a watch, is queued for it; the watch shows it after it syncs. Checkpoints are not sent to the watch yet: the GPX file has them.
- Connecting. Your Garmin email and password go to our server over HTTPS. The server signs in to Garmin with them once; if Garmin asks for a code from your two-step verification, you enter it in the same window. The password is then dropped and never written anywhere.
- What is kept. Garmin returns an access token, like the one your phone keeps after you sign in. The server stores it encrypted with a key that lives only on the server, and Garmin refreshes it from time to time.
- What it allows. A token is not limited to courses: whoever holds it can do in your Garmin Connect account what you can. No Mapa uses it only to upload a course and to queue it for your chosen watch.
- Ending it. “Disconnect Garmin” in the send window deletes the token from our server. Changing your Garmin password also ends it. Deleting your No Mapa account deletes it too.
- Risks. This is unofficial: Garmin may change its sign-in and break it without warning, and its terms do not cover this kind of access. If you are not comfortable with that, use “Download GPX” and import the file in Garmin Connect yourself.
Limitations
- The map is as good as OpenStreetMap is complete. The router learns about a new trail or a closed road only after the next data update.
- Elevation comes from terrain models. Short steep pitches can be smoothed, and total climbing may differ from your watch by 5–10%.
- The steepness limit is soft: it steers around steep parts when it can, but does not forbid them.
- Riding time and surfaces without an OpenStreetMap tag are estimates.
- Routes are suggestions. Check closures, access signs and conditions on the spot.
Found a route that goes the wrong way, a setting that does not do what it says, something slow? Use “Send feedback” at the bottom of the panel or in the help (?) window: every message is read.
Account and data
The map, routing and links work without an account. Your routes are then kept only in this browser. When you share a route or sign in with a route open, a copy of that route is stored on our server under a random short link, so the link opens it; without an account it is not tied to you, up to 25 links a day from one address.
Signing in with Google lets you keep routes on our server and open them on any device. From Google we receive only your name, email address and a stable account identifier; we do not get your contacts, files or anything else.
What we store: your name and email; the routes, tracks and checkpoints you save; short links you create; feedback you send, with the details you choose to attach; if you connect Garmin, an encrypted access token for it (your Garmin password is used once to connect and is not stored); a session cookie that keeps you signed in for 30 days. We do not sell or share this data and do not use it for advertising. Apart from Google Analytics described below, there are no third-party trackers in the planner.
Limits: up to 1,000 routes and tracks or 25 MB per account, 50 short links and 15 Garmin sends a day.
Deleting: “Delete account” in the account menu removes your account and everything stored for it at once. Short links you shared stop working. For questions write to nomapa@alexe.pt.
Where: the server is in the European Union (OVH).
Who runs it: Alexe Politov, a private person. Your data is processed to provide what you ask for (keeping and syncing your routes), and for no other purpose.
Analytics. To see which features are used and where the planner breaks, it counts actions with Google Analytics: for example that a route was built, a GPX downloaded or a setting changed, with the route type and the length rounded to 5 km. It never sends coordinates, the map position, route or place names, your name or email; the page address is sent without the part after #, which holds the map position. On your first visit the planner asks whether Google Analytics may set cookies. Until you allow it, and after “No cookies”, it runs in Google’s consent mode without cookies and sends only anonymous counts. Google signals and advertising features are off. You can change your choice any time under “Cookie settings” in the account menu. Google’s privacy policy applies to what Google receives.
Cookies and browser storage.
nc_session: keeps you signed in, set only when you sign in, 30 days. Removed when you sign out.nc_oauth: protects the Google sign-in against forgery, lives 10 minutes during sign-in._ga,_ga_HDTV62D1ZM: Google Analytics, set only if you allow analytics cookies; they tell visits of the same browser apart, up to 2 years.- Browser storage (IndexedDB, localStorage, sessionStorage) on your device: your routes and tracks, the last map view, chosen layers and settings, the route open in the tab, your cookie choice, and lists of photos found along routes (links only, kept up to 30 days). It never leaves the browser unless you sign in and sync.
Other services your browser contacts: map tiles and the heatmaps come from their providers (OpenStreetMap and CyclOSM, OpenTopoMap, mapy.com, Google, Esri, Microsoft Bing, Yandex, Waymarked Trails, Ride with GPS, AWS terrain tiles). With points along the route switched on, it also loads OpenFreeMap tiles for the route corridor, asks Wikimedia Commons for photos near the route; springs (from OpenStreetMap via Overpass) and street photos from Mapillary and Panoramax come through our server. Like any web request, they see your IP address and which map area is loaded; their own privacy policies apply. Google sees your sign-in only if you choose to sign in with Google; Garmin only if you connect it.
How long: routes and the account stay until you delete them. Server logs with IP addresses are kept for security and overwritten as they fill up (at most 30 MB per service), usually within days to a few weeks. Cached routing answers hold no personal data.
Your rights: under the GDPR you can get a copy of your data, correct or delete it, and object to its processing. “Delete account” removes everything at once; for anything else write to nomapa@alexe.pt. You can also complain to the Portuguese data protection authority (CNPD).
Map data © OpenStreetMap contributors. Heatmap © Ride with GPS. GPS traces: public GPS traces uploaded to OpenStreetMap. Passes: OpenStreetMap and the FSTR classifier. Routing: BRouter by Arndt Brenschede. No Mapa began as a rebuild of nakarte.me by Sergey Orlov. Weather: NOAA GFS. On your first visit the map opens on your approximate city, found on our server with IP Geolocation by DB-IP; the address is not stored.