This document introduces QualityStreetMap.org and OSMQA, which aim to make map editing more efficient when raster data is available. OSMQA allows volunteers to select an area to work on, load OSM data, improve it, and provide feedback on completed work. It is built using PostgreSQL, PostGIS, MapServer, MapFish Server, GeoExt, and OpenLayers. Future plans include supporting a global extent, adding layers dynamically, customizing quality grids, user login, and allowing areas to be divided.

1. Introducing QualityStreetMap.org
and OSMQA
How can we make maps more efficiently
when raster data sources are available ?
How do we keep track of the places that have been fixed
after a selective bulk import ?

2. QualityStreetMap workflow
 Select working area
 (Reserve this area) - optional
 Load OSM data from this area in editor
 Improve this data / Upload to OSM servers
 Say what you've completed in this area
 (Unreserve this area) - optional

3. 1) Select working area

4. 2) Reserve this area

5. 3) Work on this area

6. 3) Work on this area

7. 4) Provide feedback on what's
been completed

8. 5) Unreserve the area

9. D day + 3 … Lausanne highways

10. D day + 3 … Lausanne buildings

11. D day + 3 … Pontarlier

12. OSMQA

13. OSMQA building blocks
 PostgreSQL / PostGIS
 MapServer
 MapFish Server
 GeoExt
 OpenLayers

14. OSMQA features
 REST API
 I18n
 Javascript build mechanism
 Simple deploy system with config file

15. Roadmap / ideas for the future
 World extent
 Add WMS layers on the fly
 Custom & throwable quality grids
 Dimension
 Extent
 Tags
 User login (oauth)
 User has the ability to divide a tile into 4
 ...

16. Thanks !
Feel free to send comments & patches ...
François Van Der Biest
francois.vanderbiest@gmail.com
Twitter @fvanderbiest
http://code.google.com/p/osmqa/