OpenStreetBugs
From OpenStreetMap Wiki
OpenStreetBugs (http://openstreetbugs.schokokeks.org/) is a website for easily marking errors in the OSM data.
The idea is to provide a super-simple interface for users who are not going to learn to edit maps. The "bug" reports can be processed by people who have learnt to edit maps. Advanced users can also use the OpenStreetBugs-Plugin in JOSM to report bugs.
Users can leave a short message on the map if something is missing or obviously wrong, like "oneway in wrong direction" or "bridge or level_crossing?". Someone will go there and check this.
The new version begun to run form April, 2009. See User:Emka/new OSB for the detail information about the new server.
If you are using the first implementation on Appspot, the data is stored in the new database. Please use the new version in your apps, the first implementation could be shut down soon. The API should be the same.
Contents |
Quick Guide to OpenStreetBugs
OpenstreetBugs is a very simple tool to mark erroneous details on the map. You don't have to register to use it.
Tip: a map image generated by Tiles@home is sometimes more up-to-date than the pre-installed Mapnik image.
OpenStreetBugs works just like the OSM map. The mouse pointer changes into a small + sign (Symbol 4) when it is hovering on the OpenStreetBugs map. Move the map to the location of the error by dragging and click on the point where you found the error. You will then see a red circle with an (X) (Symbol 1), and a speech bubble appears for your comment. In the "your Nickname" input box, type your own name or tag in "Nickname or name“. This makes it easier to sort the comments when several people report the same error. In the "description" input box, write your description for the error. For example, write: "The street name should be 'Hadford Way', not 'Hatfield Way'". When you click OK, your error comment is stored in the map. Additional comments can be added later, but changes to the saved comments are not allowed.
When an error has been corrected, the comment can be closed (click 'Mark as Fixed'). The red point will then change into a blue point with a tick (Symbol 3), and disappears automatically after a week. Until then the comments remain visible.
Small FAQ
How does it work?
- The client side is written in AJAX, mainly based on OpenLayers.
- The server side (http://openstreetbugs.schokokeks.org/) is written in Python, the database is MySQL.
- The first implementation was using GoogleAppEngine, the database was stored on BigTable (GoogleAppEngine).
Who developed it ?
The idea and first implementation has been developed by Xav. You can find his email if you search in the Talk archives or write him via his user page. The second implementation was started by Christoph Böhme and continued by Emka. You are invited to contribute code!
Does it use the OSM database?
No, this is intended to have both databases, the OpenStreetBugs (OSB) data and OSM, separated. The authors don't believe that the tags like 'road' and 'FIXME' should be used by OSB.
Do we have a backup of the notes?
You can download daily dumps. There is also an automatic daily backup, but do not rely on that.
Can I use OpenStreetBugs with my Garmin device?
Yes, you can add POI markers to your map file.
How can I add OpenStreetBugs to my application / map?
There is a new JavaScript client that is easy to integrate into an OpenLayers map. If you want to implement your own client library, take a look at the description of the current API.
Reports
On the page OSB_Reports bugs are provided in GPX and HTML format.
Convert the sql dump to osm-xml
With a little C-Program it is possible to convert the daily sql-dumps directly to osm xml.
Get the Sourcecode here: http://tuxcode.org/john/osbsql2osm/osbsql2osm-latest.tar.gz
You can find more information here: DE:All_in_one_Garmin_Map#Openstreetbugs
Development
The source-code of this version of Openstreetbugs is distributed under the terms of GPLv3. Check it out at http://github.com/emka/openstreetbugs/tree/master
Patches are welcome! Please keep the goal of OSB in mind when thinking about new features.
