MapDust (MapDust.com, Skobbler GmbH) is an interface to report bugs (problems) that relate to OpenStreetMap. The intention is to enable the widest possible range of people to improve the OpenStreetMap database regardless of their technical skills. Although similar to other Quality Assurance tools, particularly Notes, MapDust differs in the type of bugs most frequently reported. Due to its inclusion in the iOS app, Skobbler Navigation, there is a focus on reporting issues related to navigation. The website provides interactive routing in the bug details view.
- 1 Features
- 2 Criticism
- 3 Usage
- 4 Screenshots
- 5 FAQ
- 5.1 Where can I add bugs to MapDust?
- 5.2 Where are the bugs stored?
- 5.3 Who will take care of my bug reports?
- 5.4 Is there an API for 3rd party software?
- 5.5 What happens to invalid or irreproducible bugs?
- 5.6 Under what licence are bug reports distributed?
- 5.7 Are there statistics on creating and closing bugs?
- 5.8 Are there any user terms for using MapDust?
- 5.9 Who has developed MapDust?
- 5.10 Why are some bug reports of limited quality?
- 5.11 What does "bug relevance" mean?
- 5.12 How can I test the routing behaviour around a bug?
- 5.13 What if a bug is software related rather than a problem at map level?
The main features of MapDust are:
- Bug actions: View, Close, Invalidate/Reject, Reopen, Add comment
- Bug statistics
- Bug filter
- Routing information for navigation related bugs
- Interactive routing in bug details view to verfiy routing behaviour
- Downloadable database of open bugs (Data Dumps)
- Full feature set available via API
The signal-to-noise ratio on Mapdust can be notoriously low. Few helpful reports on actual problems in OpenStreetMap are buried under large numbers of useless reports with only machine-added comments providing no insight whatsoever, complaints about (actual or apparent) malfunctions of Skobbler's software, recent changes allegedly missing in OpenStreetMap (but actually only in the outdated map on the user's device or just not included in Skobbler's rendering style), and duplicate reports. The manufacturer and provider of Mapdust, Skobbler GmbH, has not reacted to any requests for improvement on these issues for years.
Adding a new bug
In order to add a new bug left click on the desired place on map. You need to provide your nickname and a short but meaningful comment for the bug. Only comments with valid nickname and description will be accepted.
Closing or Invalidating a bug
Once you have reviewed a bug report and made any relevant changes to the OpenStreetMap data, you should either close the bug by selecting "Mark as fixed" or invalidate the bug by selecting “Mark as non-reproducible”. You will be asked to provide a short comment - something simple describing any changes made or in the case of an invalid bug, a request for additional information, will suffice.
Download data dumps
The data dumps are daily and they contain all open bugs from the system in that moment. The data format is SQL that includes also the commands to create/fill the tables besides. The structure of the data: two tables, one with the bugs ("osmexportbug") and another with the bug comments ("osmexportcomment"). File naming: the latest dump is always available as "latest_mapdust.sql.tar.gz". Older dumps (from the last week) are also available as "YYYYMMDD_mapdust.sql.tar.gz"
Viewing bugs in JOSM
- Main article: JOSM/Plugins/MapDust
- Bug actions: View, Close, Invalidate/Reject, Reopen, Add comment, Add bug
- Bug details on four tabs: (1) Bug Details, (2) Address/Location, (3) Description, (4) Comments
- Online- & Offline-Mode
- Bugs via map selectable
- Filter for visible bugs
Creating a custom Geo-RSS-feed
In order to establish a RSS-feed that shows new bugs in a certain area
- Create a map view on the area that is desired. Either search an address and zoom in/out or pan and zoom the map until the desired area is shown on the screen.
- Choose the filters accordingly on the three tabs "Status", "Type" and "Content"
- Click on the large Geo-RSS-feed button to get the link.
- Use the feed link in your preferred RSS-reader.
The Geo-RSS-feed will show all new bugs that belong to the selected area AND are in line with the filter settings.
Where can I add bugs to MapDust?
Where are the bugs stored?
The bugs are stored in a database that is operated by skobbler.
Who will take care of my bug reports?
OpenStreetMap community members can use the bug reports to improve the maps. Bugs can be displayed via the web, a Geo-RSS-feed or as layer in JOSM.
Is there an API for 3rd party software?
There is an API that is beta state currently. If you are interested in using the API request your key at info [at] skobbler.com.
What happens to invalid or irreproducible bugs?
If a bug is obviously invalid or irreproducible for whatever reason just change the bug report to "invalid". Don't hesitate to invalidate a bug.
Under what licence are bug reports distributed?
Bug reports are licenced under a Public Domain licence (Public Domain Dedication and License - PDDL) - no need for attribution or any more restrictive conditions as they soley serve as input/hint where an adjustment of the map is required.
Are there statistics on creating and closing bugs?
The MapDust-Homepage cantains several statistics, which are continously extended.
Are there any user terms for using MapDust?
Who has developed MapDust?
MapDust is developed and maintained by skobbler
Why are some bug reports of limited quality?
Many problems are reported through the feedback channel of the skobbler turn-by-turn navigation. Some of those users experience a problem during the route guidance and report the problem. However, not all users are aware of which information has to be provided in order to fix a bug. On the one hand this channels increases the volume of reports, on the other hand this channel reduces the quality of the bug reports.
What does "bug relevance" mean?
The bug relevance indicator tries to automatically evalute the completeness of the information that is required to fix the bug. "High" means that probably most information are available in the bug report to solve the problem. "Low" means that most likely additional information are required to solve the problem.
How can I test the routing behaviour around a bug?
The bug details view contains a tab called "interacting routing". You can change start and end position of the route to see how the route changes.
Please close the bug as software bug [Close as software bug].