Uber Pedestrian Data Improvements around Key Venues

From OpenStreetMap Wiki
Jump to navigation Jump to search

Background

Uber is conducting organized editing in OpenStreetMap to improve pedestrian map quality and support more reliable walking navigation for pickup and dropoff around key venues.

This activity is focused on improving the coverage and quality of pedestrian data in US and Non US Countries around key important locations and venues, with particular attention to sidewalks, crosswalks, and related pedestrian access features. The goal is to improve the completeness and accuracy of pedestrian infrastructure used in walking navigation.

Goal

The goal of this activity is to improve pedestrian map quality and support more reliable walking navigation for pickup and dropoff in the Uber app by improving the completeness and quality of:

  • Sidewalks
  • Crosswalks
  • Related pedestrian access features

Based on Uber's analysis of walking navigation quality in US and Non US Countries, we have identified gaps in sidewalk coverage, crosswalk connectivity, and pedestrian access paths, particularly near high-frequency pickup and dropoff locations listed below. These gaps result in suboptimal or inaccurate walking directions for riders and add additional complexity and frustration to the users when they want to be safely picked up or dropped of at high traffic venues and events. This activity aims to address those specific deficiencies where supported by the latest aerial and street-level imagery.

Timeline

Start date: 2026-08-12  ; End date: 2026-12-12

This page documents the initial list of venues that we plan to improve during this period. Any continuation or expansion of the targeted venues beyond this period will be documented on this page or on follow-on activity pages, as appropriate.

Organizer

UBER

Contact

Please contact the Uber OSM team through the contacts listed on Uber's organised editing Github page, or through changeset comments on edits associated with this activity.

You can also write to us : OSM@uber.com

Hashtag

Edits associated with this activity will use the changeset hashtag "#UberPedestrian''

Location

# Location Type Cities Countries/Regions
1 Educational Facilities (Universities and Colleges) Los Angeles, Pomona, Cookeville, Coventry USA, UK
2 Major Railway Stations & Transit hubs New York City, Chicago, Philadelphia, Boston, Newark, London, Paris, Madrid, Rome, Milan, Amsterdam, Stockholm, Zurich, Frankfurt, Brussels, Lisbon, Melbourne, Hong Kong, Mumbai USA, UK, France, Spain, Italy, Netherlands, Sweden, Switzerland, Germany, Belgium, Portugal, Australia, Hong Kong, India
3 Airports & Airport Transit Chicago, New York (JFK), Mumbai USA, India
4 Cruise Ports & Ferry Terminals Miami, Port Canaveral, Port Everglades, Barcelona, Rio de Janeiro USA, Spain, Brazil
5 Stadiums & Sports Arenas New York City, Chicago, San Francisco Bay Area, Los Angeles, Boston, Washington DC, Dallas, Nashville, Toronto, London, Madrid, Buenos Aires, Mexico City USA, Canada, UK, Spain, Argentina, Mexico
6 Convention & Exhibition Centers Houston, Las Vegas, Seattle, Paris, Melbourne, Hong Kong USA, France, Australia, Hong Kong
7 Entertainment Districts & Event Venues Las Vegas, Miami, Chicago, New York City, Denver, Orlando, London, Stockholm, Athens USA, UK, Sweden, Greece
8 Shopping Districts & Retail Centers New York City, Miami, Las Vegas, Anaheim, London, Paris, Dubai, Hong Kong, Perth USA, UK, France, UAE, Hong Kong, Australia
9 Tourist Attractions & Landmarks Orlando, Anaheim, San Francisco, Paris, Rome, London, Stockholm USA, France, Italy, UK, Sweden
10 Hotels & Hospitality Venues Chicago, Las Vegas, Miami, Seattle, Paris USA, France
11 Business &Ccommercial Districts New York City, Miami, London, Sydney, Riyadh USA, UK, Australia, Saudi Arabia
12 Urban Public spaces & Parks Chicago, Miami, San Francisco, Los Angeles, Washington DC, Calgary USA, Canada
13 Mixed-Use Neighborhoods & City Centers New York City, Miami, Denver, Nashville, Las Vegas, London USA, UK
14 Bus Terminus Rio de Janeiro, São Paulo, Madrid Brazil, Spain
15 Across Regions Zagreb Croatia

Tools and Data Sources

Edits will be performed manually by human editors.

Candidate Identification

Potential areas for review may be identified using Uber's internal datasets, such as GPS probe data and street-level imagery. These datasets are used only to identify candidate locations for review and are not used as the basis for OpenStreetMap edits.

Editing Sources

Editors verify candidate locations using the following imagery sources, depending on availability and recency:

  • Bing aerial imagery
  • Esri aerial imagery
  • Mapbox aerial imagery

Edits are made only where the available imagery provides sufficient confidence and in accordance with OpenStreetMap community guidelines and local mapping practices.

Editing Approach

This activity is focused on reviewing and improving existing pedestrian data and adding missing pedestrian features where supported by imagery.

Examples of intended edits may include:

  • Adding missing sidewalks
  • Improving sidewalk geometry or connectivity
  • Adding or correcting crosswalks
  • Improving pedestrian access connectivity related to walking approaches for pickup and dropoff

Editors will follow applicable local mapping conventions and will avoid making edits where source quality is insufficient or where conditions appear too uncertain to map confidently.

Editing Workflow

  1. Candidate locations are identified using internal signals and datasets.
  2. Editors review the target area using approved aerial imagery (e.g., Bing, Esri, Mapbox, or Vexcel, depending on availability and recency).
  3. Before editing, editors review existing OSM data and recent changeset history to avoid overwriting recently verified community contributions.
  4. Edits are made only where the available imagery provides sufficient confidence.
  5. All changesets will be tagged with the activity hashtag #UberPedestrian.

Quality Assurance

Uber's organised editing is performed by trained human editors and follows internal quality assurance processes.

Edits made as part of this activity will be reviewed for completeness, geometry, tag consistency, and alignment with local mapping practice. Where recent construction, temporary conditions, or unclear imagery make a feature uncertain, the feature may be left unchanged.

Participants

This activity will be carried out by the following Uber editor accounts

Community Engagement

Based on the Community Consultation. Here is the Country wise Updates and Status

S No Country/Region Consultation Status Note:
1 USA Posted to Community As per the community suggestion, PWG Bronze schema will be used for mapping sidewalks in US
2 Croatia Posted to Community
3 Brazil Awaiting to initiate Community Consultation
4 India Awaiting to initiate Community Consultation
5 Spain Awaiting to initiate Community Consultation
6 Canada Awaiting to initiate Community Consultation
7 France Awaiting to initiate Community Consultation
8 Australia Awaiting to initiate Community Consultation
9 Sweden Awaiting to initiate Community Consultation
10 Italy Awaiting to initiate Community Consultation
11 Hong Kong Awaiting to initiate Community Consultation
12 Greece Awaiting to initiate Community Consultation
13 UAE Awaiting to initiate Community Consultation
14 Saudi Arabia Awaiting to initiate Community Consultation
15 Portugal Awaiting to initiate Community Consultation
16 Belgium Awaiting to initiate Community Consultation
17 Argentina Awaiting to initiate Community Consultation
18 Switzerland Awaiting to initiate Community Consultation
19 Mexico Awaiting to initiate Community Consultation
20 UK No edits will be performed
21 Germany No edits will be performed
22 Netherlands No edits will be performed

Work Status

S No Country/Region Work Status Start Date End Date
1 USA Started 2026-08-20 NA
2 Croatia Planned 2026-08-14 NA

Changeset Comments

Uber commits to acknowledging and responding to all changeset comments and community questions related to this activity within 3 business days.

Questions about specific edits should be raised through OSM changeset comments where possible.