18
OSM and CityGuide. Quality Assurance for Navigation Software Kirill “Zkir” Bondarenko SotM Baltic, 2013

OSM and CityGuide . Quality Assurance for Navigation Software 

  • Upload
    lot

  • View
    26

  • Download
    0

Embed Size (px)

DESCRIPTION

OSM and CityGuide . Quality Assurance for Navigation Software . Kirill “Zkir” Bondarenko SotM Baltic, 2013. CityGuide (1). Navigation software Rendering Routing Address search Many other features . CityGuide (2). CityGuide. Own file format *. cgmap - PowerPoint PPT Presentation

Citation preview

Page 1: OSM and  CityGuide . Quality  Assurance for Navigation Software 

OSM and CityGuide. Quality Assurance for Navigation Software

Kirill “Zkir” BondarenkoSotM Baltic, 2013

Page 2: OSM and  CityGuide . Quality  Assurance for Navigation Software 

CityGuide (1)• Navigation software

– Rendering– Routing– Address search– Many other features

Page 3: OSM and  CityGuide . Quality  Assurance for Navigation Software 

CityGuide (2)

Page 4: OSM and  CityGuide . Quality  Assurance for Navigation Software 

CityGuide

• Own file format *.cgmap• One *.cgmap file is usually region of a country• Osmcgmap: regular updates for Russia and

some other countries

Page 5: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Free data vs users’ needsWhat Openstreetmap data is known for

What users need

Many editorsAnybody can edit

Users do NOT want to edit maps themselves

Prone to vandalism Quality

Changes can be unpredictable

Stability

Page 6: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Test before release!

• Automated tests• The map (*.cgmap) is released only if it passes

release criteria:– Routing graph– Address search– Minor consistency (e.g. shoreline is not broken)

Page 7: OSM and  CityGuide . Quality  Assurance for Navigation Software 

http://peirce.zkir.ru

Page 8: OSM and  CityGuide . Quality  Assurance for Navigation Software 

http://peirce.zkir.ru

Page 9: OSM and  CityGuide . Quality  Assurance for Navigation Software 
Page 10: OSM and  CityGuide . Quality  Assurance for Navigation Software 
Page 11: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Test: road graph connectivity

• Basic idea:– The road graph should be connected. – Roads should be connected by common nodes.– There should NOT be isolated fragments (also

known as ‘islands’)• Also:– If we select roads by level, e.g. only hw=trunk and

hw=primary, this road graph should also be connected.

Page 12: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Isolated sub-graphs aka ‘islands’

Page 13: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Even wrong statuses!

Page 14: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Test: Major highway dead ends

• Basic idea:– Important road cannot just end with dead-

end in the countryside.– It should lead somewhere!

Page 15: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Missing road fragments

Page 16: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Missing road fragments

Page 17: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Test: Address registry

• Address registry is not corrupted– Every street and

building is related to a settlement

– Addr:street tag matches name tag of the street way

Page 18: OSM and  CityGuide . Quality  Assurance for Navigation Software 

Conclusion

• CityGuide users receive maps, which have passed Quality Assurance

QA *.osm *.cgmap

http://peirce.zkir.ru