Open Street Map and It ’ s Quality Assurance

1. Open Street Mapand It’sQuality Assurance • Department of Civil and Geomatics Engineering • Kathmandu University Dhulikhel • and LMTC, Gov. of Nepal • June 21, 2012

2. Open Street Map “Open StreetMapis all about people, doing their bit, creating an incredible resource for everybody else.” - Tim Berners-Lee, 2009

3. Presentation Outilines: • General Introduction • Facts • Licensing • Privacy Policy • Quality Assurance • Pictures • Motivations • Summary • References

4. Open Street Map • Open Street Map (OSM) is a collaborative project to create a free editable map of the world as Geo Web. • The maps are created using the data from portable GPS devices, aerial photography, other free sources, digiting the base maps, and freely distributable maps from different governmental and non-governmental bodies. • Geo-Data is freely downloadable under Creative Commons Attribution-ShareAlike 2.0 licence.

5. History • OpenStreetMap (OSM) was founded in July 2004 by Steve Coast. • In April 2006, a foundation was established with the aim of encouraging the growth, development and distribution of free geospatial data and providing geospatial data for anybody to use and share. • In December 2006 Yahoo confirmed that Open Street Map could use their aerial photography as a backdrop for map production

6. Histroy • By August 2008, shortly after the second The State of the Map conference was held, there were over 50,000 registered contributors; by March 2009 there were 100,000 and by the end of 2009 there were nearly 200,000. • Note that not all registered contributors actually contribute to the map - in March 2008 approximately 10% of the registered users were contributing to the map data each month

7. Technology • The initial map data was all built from scratch • volunteers performed systematic ground surveys using a handheld GPS units and a notebooks or a voice recorders • Collected data were then entered into the OpenStreetMap database from a computer • More recently the availability of aerial photography and other data sources from commercial and government sources has greatly increased the speed of this work and has allowed land-use data to be collected more accurately. • When large datasets are available a technical team will manage the conversion and import of the data.

8. Licensing • OpenStreetMap data is published under an open content licence, with the intention of promoting free use and re-distribution of the data (both commercial and non-commercial). • The currently used licence is the Creative Commons Attribution-Share Alike 2.0 licence • however legal investigation work and community consultation is under-way to re-license the project under the Open Database Licence (ODbL) which is more suitable for a map dataset

9. Privacy Policy Privacy Policy

10. What is Privacy Policy ? Privacy policy is a statement or a legal document (privacy law) that discloses some or all of the ways a party gathers, uses, discloses and manages a customer or client's data. • Personal information: • Things to identify an individual • name, • address, • date of birth, • marital status, • contact information, • ID issue and expiry date, • financial records, • credit information, • medical history, • where you travel • intentions to acquire goods and services • . In the case of a business it is often a statement that declares a party’s policy on how it collects, stores, and releases personal information it collects. It informs the client what specific information is collected, and whether it is kept confidential, shared with partners, or sold to other firms or enterprises.

11. Current Privacy Policy : What personal information OSM may be gathering from you, who can see this information, and what options you have for controlling this? • GPS Trace Data • GPS data is uploaded in the form of individual GPX files. • These are kept as raw files, as well as imported into the database. GPX files can be marked "public" by the uploader. • When GPS data for an area is downloaded via the API. No indication is provided of which user uploaded a point. • GPS data downloaded in this way will include points from traces which were not marked as public. • If a GPS trace is marked as public with traces containing private information, when it is uploaded then the raw trace may be downloaded from the web site or using an API call. In this case the user's display name is shown (regardless of whether the user has made their edits public) and the timestamps in the GPX file will be included.

12. Current Privacy Policy : • Map Data • All edits made to the map are recorded in the database with the user ID of the user making the change, and a timestamp at the time of change upload. • In general all of this information is also made available to everyone via the website, including links to allow everyone to easily cross-reference which user has made which edit. • Historically OpenStreetMap offered an option to make "anonymous edits". This means the website does not display an association between edits and user ID.We intend to continue respecting the wishes of those users who (in the past) made edits in this mode, however OSM no longer allow users to make further edits in anonymous mode.

13. Current Privacy Policy : User Location If a user selects the "make my edits public" option and also sets a home location then they will appear on the "nearby mappers" list for other people with a home location near theirs.

14. Current Privacy Policy : • Email Addresses • The registered email address for an OSM user account, will never intentionally be published on the internet anywhere, shared with third party organisations, or revealed directly to other logged in users. • Email addresses will be used by the server to notify the user if another user has sent a message through the website. Only System Administrators will have direct access to email address data. It may be used by these people to contact users directly about their edits or other OpenStreetMap related issues. • Note: some other types of Accounts used by developers/communitydo expose email address information more publicly (due to technical limitations of the software used, rather than policy decisions)

15. Quality assurance Quality assurance “Quality in a service or product is not what you put into it. It is what the client or customer gets out of it.” – Peter Drucker

16. Quality assurance Are you satisfied with the data quality of OSM? What Efforts have been done to Assure Data Quality? final draft 1

17. Quality assurance • What is quality Assurance? • Quality Assurance tools help: • lead to better quality of OSM data. • Quality Assurance is: • Achieved by providing a list of bugs in the data, which mappers can then go and fix using editing tools. • The bugs are either automatically detected based on rules and data analysis, or the tools provide a means of manually reporting them, or some combination of the two.

18. Quality assurance • How this is achieved? • By Analyzing • By Improving • By Monitoring Tools: • Bug reporting tools • Error Detecting tools • Validator

19. Bug Reporting Tools Bug Reporting Tools: • These are tools that try to highlight and point out parts of the data that are likely wrong. they can provide a very valuable visualization of which areas need attention and can help spot and correct errors. • Openstreetbugs • At OpenStreetBugs (OSB), We can mark and describe bugs in OSM on a map without authentication. Hopefully someone else will notice your bug report and act upon it. 

20. Bug Reporting Tools Fig: Open Street Bugs

21. Bug Reporting Tools • MapDust • MapDust  was established to provide a user friendly and intuitive interface to collect problems, missing entities or attributes that relate OpenStreetMap. The intention is to enable the widest possible range of people to improve the OpenStreetMap database regardless of their technical skills..

22. Error Detecting Tools Error Detection Tools Error Detecting Tools check the OSM data for potential data errors, inaccuracy or sparsely mapped places. Users should check if these structures are really wrong and correct the data for a continuously rising data quality.

23. Error Detecting Tools • Keep Right • Keep Right  shows automatically detected errors on map or in list form. It has a system for reporting false positives and for labeling a bug as fixed. Keep right has rules to automatically detect the following error types: • non closed areas • dead ended one ways • almost junctions • deprecated tags • missing tags • motorways without ref • places of worship without religion..

24. Error Detecting Tools Fig: Keep Right

25. Error Detecting Tools • Osmose • Osmose, whose name means Open Street Map Oversight Search Engine, is one of many quality tools available to detect errors and inconsistencies OpenStreetMap data. • Osmose is a reporting tool error consists of two parts : • The frontend • This is the visible part for displaying an error slippy map • The backend • This is the hidden part for data analysis of OpenStreetMap of error detection.

26. Error Detecting Tools Duplicate Nodes The Duplicate nodes map  is a display showing the locations of all duplicate nodes, where two nodes are at the exact same location.

27. Error Detecting Tools

28. Error Detecting Tools JOSM Validator The JOSM Validator is a feature of JOSM which checks and fixes invalid data. For a long time it was available as a plugin, but is now a core feature of the software. There is no longer any need to install these features as a plugin.

29. Error Detecting Tools JOSM validator

30. Error Detecting Tools • Similarly, there are other error detection tools. Some are : • The Gary68 tools • Coastline Error Checker • OSM Inspector • Turn Restrictions Analyzer

31. Visualization Tools ITO Map ITO Mapis a new globalslippy overlay map service which offers a range of map views to highlight many 'hidden' data layers within OpenStreetMap. It can be used to view existing data within OpenStreetMap and also as aquality assurancetool to help improve the quality and completeness of OpenStreetMap data.

32. Visualization Tools

33. Monitoring Tools Monitoring Tools In addition to the above error and bug reporting tools, there are a number of tools that allow us to spot erroneous changes and edits. For example if we are very familiar with an area and have thoroughly mapped it, we might want to follow all changes and verify that no unintended damage or vandalism happens in the area. OSM Mapper Monitoring changes to OSM data within a defined area See who is doing edits and where Subscribe using RSS to be kept informed about changes

34. Monitoring Tools Fig Monitoring Tools, year of edits for New York

35. Screen Shots of OSM Kathmandu

36. Screen Shots of OSM Baghdad

37. Screen Shots of OSM Bangalore

38. Screen Shots of OSM

39. Screen Shots of OSM Berlin now 2012

40. Screen Shots of OSM Berlin now 2012

42. Some Photographs Not company Its Community

43. Motivation Toward OSM. • …commercial mapping products are constantly failing us up here in rural Quebec. On a number of occasions my husband and I have both wished that we could just upload our own GPS data to fix the existing maps. It's all frustratingly out of date--showing non-existent logging roads as real streets, and not showing major interurban routes. I suspect that in many rural parts of Canada neither government nor industry has any motivation to verify old data… • I spent last winter documenting some local snowshoe and ski trails and uploading that data to Google Maps. I think one would like to develop some kind of online community space with other winter sport enthusiasts in this region in order to create a useful online resource that could benefit everyone. That information is not readily available online or in print. You have to be a real explorer to find these trails.

44. Motivation Toward OSM. • I get enormous satisfaction out of this entire process as well as know that I'm contributing towards a valuable resource that others can use. I also enjoying exploring on my bike new areas that I'm mapping - I've discovered some cool suburban places that I never new existed - often within meters of roads that I drive down regularly. • Being an author of books which are using maps, I am not able to pay royalty fees to map companies like google or teleatlas. • It's a lot of fun, and it's nice to see your work appear 1-2 hours after it's done available to the whole world

45. Motivation Toward OSM. • …because I find that my country is less detailed than other foreign countries and I want to participate to get it as detailed as the others (see it as a kind of race ;-) • When Google released the tool more broadly last year, Faraz Ahmad, a 26-year-old programmer from Pakistan who lives in Glasgow, took one look at the map of India and decided he did not want to see his homeland out-mapped by its traditional rival. So he began mapping Pakistan in his free time, using information from friends, family and existing maps. Mr. Ahmad is now the top contributor to Map Maker, logging more than 41,000 changes. New York Times (November 17, 2009)

46. Summary • Majority of contributors are educated young males • Instrumentality of local knowledge as a key determinant of contribution (i.e. representation of local area; accuracy of map; self efficacy; fun) • Large number of people make few contribution • OSM community are committed for the quality assurance • There are many research going on in this issue

47. References: • https://www.openstreetmap.org • https://www.creativecommons.org/licenses/by-sa/2.0/ • https://wiki.openstreetmap.org/wiki/quality_Assurance • https://www.onlinelibrary.wiley.com • A Quality Analysis of OpenStreetMap Data (M.Eng.Dissertation), Aamer Ather – May-28,2009

48. Open Street Map: Let’s GO MAPPING

49. Thanks for listening!