Grab

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Grab
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

Grab is a Singapore-based technology company that offers ride-hailing, ride sharing and logistics services through its app in Singapore and neighbouring Southeast Asian countries.

They are a Gold Corporate Member of the OSM Foundation.

Grab - OSM Support and Usage

Grab would like to be part of the OSM community and help improve the map. Many places might not be accurate or identifiable on other forms of maps. Having these places improved by Grab will give richer information to OSM mapping contributors.

OSM Usage - Grab's data team contributes to OpenStreetMap's coverage of a number of countries. The team's mapping projects are documented publicly in the Grab Data Projects repository on GitHub. Grab's applications make use of OpenStreetMap data in few areas of South East Asia where commercial data providers have less extensive coverage.

OSM Data Mapping Guidelines

Data Modelling

The primary focus of work is adding missing roads and adjust alignment thereby enhancing the existing data in OSM.

In some cases, the existing road network has been mapped incorrectly, meaning that some features are missing or may be in-accurately mapped. We plan to use a variety of imagery sources to help map the geometry more accurately.

We always monitor the feedback from local mappers as local knowledge always precedes.

Improvements that will be addressed include the following:

  1. Adding missing roads
  2. Adjusting road alignment as per imagery and GPS traces
  3. Validate existing tags like- classification - Residential, Trunk, Motorway etc and attributes - Bridge, Tunnel, links etc.
  4. Cities might be revisited basis new improvements and or internal requirement.

Process Flow

Here is the process followed by Grab data team while modelling roads.

  1. Grab smoothened GPS traces(internal and non-downloadable file)
  2. Find best imagery properly aligned per GPS traces and ground truth
  3. Use JOSM with GPS traces and best imagery as reference
  4. Visually identify missing roads and add them
  5. Correct classification and attribute errors in existing data
  6. Run validation and fix all errors and warnings
  7. Upload changeset with appropriate comments

Mapping Guidelines

The team's mapping projects are documented publicly in the Grab's Data Improvement Projects repository on GitHub.

Grab follows OSM's global and local policies, along with any other guidelines as appropriate.

Grab will also reach out to local OSM communities before beginning work, to gather feedback, suggestions and learn more about the data and tags used in that area.

Data sources and imagery we will use are listed here. Grab will research and use local tags and defer to local mappers, and also check the JOSM history on items to see why previous edits and changes were made.

Tools

The team will use JOSM for completing the task. JOSM has the OSM and Grab GPS traces (internal and non-downloadable file), and validation warnings for road networks and other possible issues that are important to prevent improper changes.

Changeset Comments

The team will provide changeset comments that are in compliance with OSM changeset guidelines.

Quality Process

Below mentioned is the end to end process flow along with quality check gates at each phase

QC Process Flow.png

Phase 0 - Initial Validation

  1. Check for appropriate changeset comments and ensure they are in line with the scope covered in particular upload.
  2. Check if changeset boundary does not cover a larger area and/or multiple localities / cities / countries.
  3. Either case, as changeset cannot be reverted or modified, record the instances as feedback in the internal tracker, which will be used for further feedback to the respective production.
  4. Run validation queries, if errors found, reject the changeset without further evaluation.

Phase 1 - Quality Check 100%

Different validators other than production ops will perform quality check. Follow the same process as that of production, while validating 100% of changesets marked as complete. Record the errors found and segregate basis Major and Minor errors -

Major Errors -

  1. Missing roads which are navigable
  2. Classification errors which are evident from satellite imagery on high priority roads - Motorway, Trunk, Primary
  3. Missing / Incorrect tags on above mentioned roads
  4. Incorrect alignment (>3m) as per strava heat maps (Do not micro align existing segments)
  5. Incorrect DoT(assigned / modified) on high priority roads
  6. Extra roads(created by GL users, we however do not delete existing data under any circumstances except if roads are duplicated) which are not evident from satellite imagery
  7. Incorrect connectivity which are not evident from satellite imagery

Minor Errors -

  1. Classification errors which are evident from satellite imagery on Low and Medium priority roads - Secondary, Tertiary, Unclassified, Residential and Service roads
  2. Missing / Incorrect tags on above mentioned roads
  3. Incorrect alignment (>3m) as per strava heat maps (Do not micro align existing segments)
  4. Incorrect DoT(assigned / modified) on low / medium priority roads

Meta Quality Check - 10% random sample

  1. A changeset will be marked accept when -
  2. Zero validation errors (With GL Id in history of the segment identified in validation check)
  3. Zero major errors
  4. No. of minor errors are less than or equal to 3
  5. Else Changeset is considered as reject.

Acceptance Criteria - Quality check 100%

  1. A changeset will be marked accept when -
  2. Zero validation errors (With GL Id in history of the segment identified in validation check)
  3. Zero major errors
  4. No. of minor errors are less than or equal to 5
  5. Else Changeset is considered as reject.

Feedback Mechanism

  1. Irrespective to changeset status, errors (major/minor) are documented in the internal tracker for further analysis
  2. Extensive root cause analysis(RCA) is conducted at error category level to identify the root cause and derive appropriate corrective and preventive action (CAPA)
  3. Derived action items (AI’s) will be monitored for a period of 4 weeks to measure the efficacy.
  4. If the error rate is found decreasing, implemented action item is documented as a best practice
  5. Else, root cause analysis and/or action items are found not effective, in which case analysis is conducted again with a different sample
  6. Error trend basis each operator is tracked to find out if there are repeated errors found.
  7. Appropriate actions are taken in this order -
  • Performance action plan(PAP)
  • Performance improvement plan(PIP)
  • Refer to Human Resource Team (HR)

Error Detection

Grab will use various QA and data quality tools such as JOSM validation warnings and errors, as well as best practices on data quality from the OpenstreetMap Wiki page and LearnOSM.

Grab Data Team

Grab's data team contributes to OpenStreetMap's coverage of a number of Asian cities.[1] For any questions, please get in touch with Jinal Foflia, our Senior Outreach and Community Manager

Below is a list of the team members supporting the mapping projects.

System-users-3.svganushalanka (on osm) System-users-3.svgardhavara (on osm) System-users-3.svgharishpuppala (on osm) System-users-3.svgtejan7 (on osm) System-users-3.svgstella9 (on osm) System-users-3.svgalekhya5 (on osm) System-users-3.svgkawle (on osm) System-users-3.svgsaisokam (on osm) - Left GRAB Team on 2nd Mar'18 System-users-3.svgsrivastav5 (on osm) - Left GRAB Team on 17th May'18 System-users-3.svgudaykiran3 (on osm) System-users-3.svgzakriya1 (on osm) System-users-3.svgRamanyam (on osm) System-users-3.svgMalka7 (on osm) System-users-3.svgNeethu5 (on osm) System-users-3.svgvaidha1 (on osm) System-users-3.svgnaik4 (on osm) System-users-3.svgsurya8 (on osm) - Left Grab Team on 6th Jul'18 System-users-3.svgKolla6 (on osm) System-users-3.svgRakesh9 (on osm) System-users-3.svgmotkar (on osm) - Left Grab Team on 20th Jul'18 System-users-3.svgakhil2 (on osm) System-users-3.svgmarupally (on osm) System-users-3.svgpoornima1 (on osm) System-users-3.svgrudroju (on osm) System-users-3.svgmutpuri (on osm) System-users-3.svgsaicharan1 (on osm) System-users-3.svgsabiyana (on osm) - Left Grab Team on 13th July'18 System-users-3.svgapurva2 (on osm) System-users-3.svgneela1 (on osm) System-users-3.svgrenuka1 (on osm) System-users-3.svgvijay1 (on osm) System-users-3.svglavanya1 (on osm) System-users-3.svglakkarssu (on osm) System-users-3.svgreshma6 (on osm) System-users-3.svgdasari1 (on osm) System-users-3.svgsrivani1 (on osm) System-users-3.svgsridhar1 (on osm) System-users-3.svgattili1 (on osm) System-users-3.svgalney1 (on osm) - Left Grab Team on 10th Oct'18 System-users-3.svgkonkala1 (on osm) System-users-3.svgharishm (on osm) System-users-3.svgtogirigalu (on osm) System-users-3.svgdivya_sree (on osm) System-users-3.svgprathi07 (on osm) System-users-3.svgramrom (on osm) System-users-3.svgvira_02 (on osm) System-users-3.svgpra_sad (on osm) System-users-3.svgwin_03 (on osm) System-users-3.svgjyo_1 (on osm) System-users-3.svgarvind_1 (on osm) System-users-3.svgdiv006 (on osm) System-users-3.svgsai_sri (on osm) System-users-3.svglanke_1 (on osm) System-users-3.svgravali_3 (on osm) System-users-3.svgmayi007 (on osm) System-users-3.svgfarmal (on osm) System-users-3.svgpavani_03 (on osm) System-users-3.svgaj_34 (on osm) System-users-3.svgsujatha_1 (on osm) System-users-3.svgavinash1 (on osm) System-users-3.svgdeepthi1 (on osm) System-users-3.svgnikhil5 (on osm) System-users-3.svgMarla_1 (on osm) System-users-3.svgjeeta1 (on osm) System-users-3.svgsravan7 (on osm) System-users-3.svgmudumala (on osm) System-users-3.svgjuvvanapudi_1 (on osm) System-users-3.svgkimsohyun (on osm) System-users-3.svgbeulahd (on osm) System-users-3.svgsravy (on osm) System-users-3.svgkumar3 (on osm) System-users-3.svgPranith1 (on osm) System-users-3.svgadi3 (on osm) System-users-3.svgdas2 (on osm) System-users-3.svgchintu1 (on osm) System-users-3.svgsrilekha1 (on osm) System-users-3.svgsrujana3 (on osm) System-users-3.svgravalim (on osm) System-users-3.svgbhavani1 (on osm) System-users-3.svgdevi2 (on osm) System-users-3.svgharikasid (on osm) System-users-3.svgpriyaboya (on osm) System-users-3.svgpravenya (on osm) System-users-3.svgimi007 (on osm) System-users-3.svgpolagouni (on osm) System-users-3.svgarivenid (on osm) System-users-3.svgbhavyakota (on osm) System-users-3.svgkumarip (on osm) System-users-3.svgdi_vya (on osm) System-users-3.svgteratipally (on osm) System-users-3.svgchary3 (on osm) System-users-3.svgdaram2 (on osm) System-users-3.svgvagginati (on osm) System-users-3.svganu_smita (on osm) System-users-3.svgkante_1 (on osm) System-users-3.svgsha_lini (on osm) System-users-3.svgpunya_man (on osm) System-users-3.svgsiripurapu (on osm) System-users-3.svgnadigatla (on osm) System-users-3.svgsravanthi1 (on osm) System-users-3.svgsans_r (on osm) System-users-3.svgsun_jeev (on osm) System-users-3.svgbarigela (on osm) System-users-3.svgsnigdhap (on osm) System-users-3.svgalee_m (on osm) System-users-3.svgchitra1 (on osm) System-users-3.svgman_asa (on osm) System-users-3.svgak_ram (on osm) System-users-3.svgme_vij (on osm) System-users-3.svgdhoni007 (on osm) System-users-3.svga_run (on osm) System-users-3.svgdee_ksha (on osm) System-users-3.svga_rif (on osm) System-users-3.svgpride_dara (on osm) System-users-3.svgmuqtar (on osm) System-users-3.svgjagdish30 (on osm) System-users-3.svgtahasin (on osm) System-users-3.svgbha_rath (on osm) System-users-3.svgsra_vya (on osm) System-users-3.svgkis_hore (on osm) System-users-3.svginkol (on osm) (Left GRAB team) System-users-3.svgbhav_ana (on osm) System-users-3.svgts_kanth (on osm) System-users-3.svgmadagoni (on osm) System-users-3.svggrabtaxi1 (on osm) System-users-3.svggrabtaxi2 (on osm) System-users-3.svggrabtaxi3 (on osm) System-users-3.svggrabtaxi4 (on osm) System-users-3.svggrabtaxi5 (on osm) System-users-3.svggrabtaxi6 (on osm) System-users-3.svggrabtaxi7 (on osm) System-users-3.svggrabtaxi8 (on osm) System-users-3.svggrabtaxi9 (on osm) System-users-3.svggrabtaxi10 (on osm) System-users-3.svggrabtaxi11 (on osm) System-users-3.svggrabtaxi12 (on osm) System-users-3.svggrabtaxi13 (on osm) System-users-3.svggrabtaxi14 (on osm) System-users-3.svggrabtaxi15 (on osm) System-users-3.svggrabtaxi16 (on osm) System-users-3.svggrabtaxi17 (on osm) System-users-3.svggrabtaxi18 (on osm) System-users-3.svggrabtaxi19 (on osm) System-users-3.svggrabtaxi20 (on osm)

General Feedback

For more information, suggestions, questions or general feedback contact our community lead System-users-3.svgjinalfoflia (on osm)

Thailand map errors report

After data quality issues were identified[2] in Thailand, an entry has been created to track and document errors by Grab's mapping team.

References