hoream-telenav
commented
6 years ago The role of our project was to improve the quality of the OSM features used for navigation, in Phoenix Arizona.
Starting from September till now, the whole project workflow was realized in 3 main steps:
Step 1. Research and get in touch with local community (research on local open source data, keep in touch with local OMS users, official traffic signs and driving rules, research on HOV and toll roads, roads under construction, other specific road features of Arizona State).
Step 2. Build-up process:
- Road geometry, Road Name, One Way, Gates and Other Geometric Feature (turning circles, turning loops, etc.)
- Signpost
- Turn Restrictions and Traffic Lights
- Lane and Turn Lane Info, including HOV Lanes and Toll Roads
- Speed Limit Editing.
Step 3. Quality Assurance (QA for every feature edited by our team in OSM, some road name special issues, repairing broken relations, final edits and corrections based on Improve OSM plug-in, Osmose and Keep Right errors, tile by tile verification).
The first step was a very important one because the team had to get in touch with the local community and mapping rules. Also, a research was made for finding other open source and free of charged data beside the already well-known sources used by OSM users (TIGER Roads, Bing, Digital Globe, Open Street Cam, Mapillary). The under-construction roads found in this step were permanently monitored in order to be edited later.
The second step was the most time consuming and it included the editing and reviewing of all the most important navigable OSM features, starting from motorway, trunk, primary, secondary, tertiary, residential and service ways. The whole editing process last for about 3 moths and the workflow was mainly based on tile by tile method but, we also edited based on way category or REF. During this period, we helped the community to increase the OSM quality as you can see below:
The third step was the last but not the less important. Because we wanted to have a good quality features in OSM, we had to make a closure check on our edits, already made in the build-up process and where it was necessarly, to feel the gaps. So, we used different QA procedures, script, other plug-ins, error identifiers and even tile by tile verification. Doing that, we had an important overview of our whole edits, especially of our wrong ones. In this step, we resolved also a name tag issue we’d came across during step 2, which is detailed by my colleagues, in the following link https://github.com/TelenavMapping/mapping-projects/issues/35. Step 3 represents for Telenav team also a certainty of good quality editing.
In the moment when we needed a double check for our work, the community was a good help, giving us important feedbacks. For the next months, we’ll surely keep in touch continuously with the local OSM users, looking forward for their feedback in order to keep up a good maintenance work.
In the heatmap below you can see an evolution of our edits during those 4 moths, on Phoenix, Arizona.
Description
This project is designed to improve the quality of OSM by adding various map features used for navigation, in Phoenix, Arizona.
What we map
In the following period we will focus on adding:
Sources
Government data:
Satellite imagery:
Street-level imagery
Others:
Who will be involved
Telenav mapping team