DMD2

DMD2
Author:	DMD Navigation
License:	Proprietary (freemium)
Platform:	Android
Status:	Active
Languages:	English, Catalan, Czech, Danish, German, Spanish, French, Hungarian, Italian, Norwegian Bokmål, Dutch, and Polish
Website:	https://dmdnavigation.com
Install:	Google Play
Offline navigation for adventure and off-road travel: motorcycles, 4x4 cars and vans, RVs, ATVs and side-by-sides.
Features Feature Value Map Display Display map yes Map data vector;raster Source offline;online Rotate map yes 3D view yes Shows website ? Shows phone number ? Shows operation hours ? Routing Routing yes Create route manually ? Calculate route yes Create route via Waypoints yes Routing profiles road (fast or curvy), off-road (very easy to hard) Turn restrictions ? Calculate route without Internet (Offline routing) yes Routing providers BRouter Avoid traffic ? Traffic Provider ? Navigating Navigate yes Find location yes Find nearby POIs ? Navigate to point yes Navigation with voice / Voice guidance yes Keep on road yes Lane guidance ? Works without GPS ? Navigate along predefined route yes Tracking Make track yes Customizable log interval ? Track formats gpx Geotagging ? Fast POI buttons ? Upload GPX to OSM yes Monitoring Monitoring ? Show current track ? Open existing track yes Altitude diagram yes Show POD value ? Satellite view ? Show live NMEA data ? Show speed yes Send current position ? Editing Add POIs no Edit / Delete POIs no Add way no Edit geometries no Edit arbitrary tags of existing OSM objects yes Edit relations no View notes no Create notes yes Edit notes ? Work offline ? Support imagery offset DB ? Upload to OSM yes Rendering ? Accessibility Accessibility support ? Complete non graphics text output ? Braille interface ? Exploration modus ? Public Transport mode ? Danger Warnings yes Screenreader ? Screenreader languages ?

DMD2 is a navigation app for adventure and off-road travel (motorcycles, 4x4 cars and vans, RVs, ATVs and side-by-sides), made by DMD Navigation (dmdnavigation.com). It runs on rugged handlebar and dashboard units and on Android phones. Its offline maps, place search and routing are built from OpenStreetMap data.

Improve the Map (OSM editing)

Users edit OpenStreetMap with their own OSM accounts. They answer quick questions while riding or driving (one tap on the screen or on a handlebar remote), or for a road they long-press on the map when stopped. Nothing is sent until the user looks over the answers and sends them. While the mode is on, the app keeps a trail of the ride on the device so that an answer can cover a whole road. This trail is never uploaded, and it is deleted after a week or when the mode is turned off. The only GPS data ever uploaded is the stretch of a missing track the user recorded, and only if they agree.

What users can edit

User action	OSM result
Surface	surface=*: asphalt, compacted, gravel, dirt, sand, rock, grass
Condition	smoothness=*, with the words of the smoothness page for the user's vehicle. Motorcycles: intermediate (touring), bad (standard motorcycle), very_bad (big adventure bike), horrible (dual-sport), very_horrible (enduro), impassable. Four wheels: intermediate (any car), bad (normal car), very_bad (SUV), horrible (real 4x4), very_horrible (ATV / SSV only), impassable.
Track type	tracktype=*: grade1 to grade5 (solid / mostly solid / mixed / mostly soft / soft), on highway=track only
Width	est_width=*, named by the widest vehicle that fits: 1 (bike only), 1.5 (ATV), 2 (side-by-side), 2.5 (car / 4x4), 3 (van / RV), 5 (two lanes). Tracks, paths and small roads only; never where width=* is set.
Sign	4wd_only=yes; motor_vehicle=*, motorcycle=*, motorcar=*, motorhome=* or atv=* = no; access=private. Only from a sign, only ever stricter, and only after the user confirms it.
Report	an OSM note at the spot: gate, blocked, ford, washed out, low clearance
Gate or ford on the map	a node on the way with barrier=gate or ford=yes, only where its position is certain and only after the user confirms it (see below)
Missing track	an OSM note where the track leaves the mapped roads, with a GPS trace of the recorded stretch if the user agrees (see below)

How an edit is made

1. While riding or driving, the user taps an answer; when stopped, they can long-press a road on the map and answer for it. The app records the answer with the position and the road DMD's own map shows there. Nothing is sent while moving.
2. The user looks over the list and sends it. The app matches each answer to the current OSM way (its offline maps carry no OSM ids) and checks it against live data.
3. Answers are uploaded as one changeset per area, under the user's own account. Reports are opened as notes; a gate or ford put on the map is a changeset of its own.

Missing tracks

Since DMD2 4.028 a user can record a track that is not in OpenStreetMap while riding it:

1. Where the track leaves the map, the user starts Missing Track; at its end, they stop it. The app keeps the GPS fixes of that stretch only: a point every 8 m or more, skipping fixes less accurate than 25 m. A stretch under 50 m is not saved. A forgotten recording stops by itself after 30 km or 3 hours, or when the ride ends.
2. When the user sends it, the app first reads live OSM data along the whole stretch. If less than a quarter of it (or less than 50 m of a short one) is more than 25 m from a mapped road (any highway=* except proposed, abandoned, razed, disused or dismantled), the track is already mapped and nothing is sent.
3. Otherwise it opens a note where the track leaves the mapped roads, for example: "A track that is not in OpenStreetMap passes here. It starts here and runs for about 1.2 km, ending near 41.20123, -8.29457." An open note within 50 m saying the same stops a duplicate.
4. If the user agreed to send GPS traces (asked once, before the first one; they can also send the note alone), the recorded stretch is uploaded first as a GPS trace and the note links to it. The trace is identifiable (listed under the user's name, with timestamps), so a mapper can open it from the note. Its description reads "A track missing from OpenStreetMap, about 1.2 km, recorded on a motorcycle ride with DMD2 #DMD2" and its tags are "DMD2" and "missing track". Only the recorded stretch is sent, never the rest of the ride.

Since DMD2 4.029, with Improve the Map mode on, the app also notices when the user has ridden about 300 m where DMD's own map shows no road (only where a downloaded map covers the area). It asks once, by voice and on screen, whether to record a missing track; if the user says yes, the recording starts where the road ended, with the stretch already ridden. If they let it pass, it stays quiet for 10 minutes.

DMD2 never draws the track itself: a local mapper decides whether and how to map it.

Gates and fords

Since DMD2 4.029, a Gate or Ford report can become a node on the road instead of a note, but only where its position is certain, and only after the user confirms it:

• Gate (barrier=gate): where a mapped barrier=fence, wall or hedge crosses the road within 20 m of the report; or where the user stopped at it (at walking pace, at most 12 m from the road, with a GPS accuracy of 15 m or better); or where the user long-pressed the road on the map.
• Ford (ford=yes): where a mapped stream, river, brook, ditch, drain or canal crosses the road within 40 m of the report. Never where the road or the waterway is a bridge, a tunnel or a culvert, or has a layer=*.
• At a crossing, a node the two ways already share gets the tag; otherwise a new node is added to both ways where they cross. On the road alone, an untagged node within 3 m gets the tag; otherwise a new node is added to the road.
• Nothing is added within 5 m of a junction, on roads above highway=tertiary, or when OSM already has a gate within 25 m (a ford within 40 m, or ford=* on the way).
• Before sending, the app shows where the node would go ("where the fence crosses the road", "where you stopped"); the user can add it, send a note instead, or remove the report. Anything less certain, such as a gate passed at speed or a ford with no mapped waterway, goes as a note, as before.

Each node is its own changeset, for example "Gate where a fence crosses a track, surveyed on a motorcycle ride".

Safeguards

• Own accounts only (OAuth 2.0 with PKCE). No shared or bot account. Permissions asked: read_prefs, write_api, write_notes and write_gpx (the last one for missing tracks; users who signed in before DMD2 4.028 are asked to sign in again before their first trace).
• Only values the user chose from a fixed list. Nothing is inferred from speed, sensors or other users' data.
• Missing tags are filled in; changing an existing value, or a combination that contradicts the way's other tags, needs an extra confirmation.
• An answer covers the whole way only when the way is up to 1 km long, the user's ride covered at least half of it, or the user confirms it. Since DMD2 4.029, the user can instead send it for the part they rode: the way is split where the ride began and ended (at an existing node within 5 m, else a new one; the longest piece keeps the way's id, and route relations get the new pieces in order), and only that part gets the tag. A part under 50 m, a closed way, or a way in a turn restriction is not split.
• Width is only ever an estimate (est_width=*) and never replaces a measured width=*.
• Access is never loosened. Restrictions are only added from a sign, after the access hierarchy is checked (access=no already covers motorcycle=no), and each one needs the user's confirmation.
• Reports become notes, one per report; an open note within 50 m saying the same stops a duplicate. A gate or ford becomes a node only where its position is certain (see above), after the user confirms it.
• highway=* is never changed. No "mud" and no temporary conditions.
• Source: the user's own survey. Every answer needs a live GPS fix, and rides replayed by the app's route simulator never reach OSM.
• If a way changed since it was downloaded, each tag is checked again and conflicting answers are dropped.
• Undo within 12 hours (a new changeset restores the previous values or removes a gate or ford the user added; or the note is closed and a missing track's GPS trace is deleted), unless someone changed it since. Tested on the development API before release.

Changeset tags

• created_by=DMD2 <version>
• hashtags=#DMD2
• source=survey
• locale=*: the user's language
• comment=* in plain language, for example "Surface and smoothness of 12 tracks, surveyed on a motorcycle ride", "Ford where a stream crosses a track, surveyed on a 4x4 ride" or "Surface of part of a track (split where the ride began and ended), surveyed on a motorcycle ride"
• review_requested=yes on a user's first five changesets

Following and contacting

• To follow the edits, filter changesets by editor "DMD2" on OSMCha. They also carry the hashtag #DMD2, as do the notes and the GPS traces (traces are also tagged "DMD2").
• Contact: DMD Navigation on openstreetmap.org (send a message from the profile page), or info@dmdnavigation.com. We answer changeset comments within two working days.
• This is an editor users choose to use themselves. If DMD ever promotes mapping in particular places (suggestions or campaigns), we will publish an Organised Editing page first, as the guidelines require.

Attribution

DMD2 shows "© OpenStreetMap" in a corner of the map, and the full credit with a link to openstreetmap.org/copyright in Settings → Map Data Credits.