Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Mapbox HOV Lanes Project

Offen
  • Stimmt etwas nicht?
#435 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
data

Rechercherichtung

No code files or specific road segments are identified. Read the linked OpenStreetMap HOV and conditional-restriction guidance, then use the iD Editor and the stated imagery and other compliant sources to assess a specific corridor; do not guess where evidence is unclear. Work is tracked with #mapbox_hov, and the project reports corrected segments and verified access points after completion.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Introduction

The Mapbox HOV Lanes project focuses on mapping and refining High-Occupancy Vehicle (HOV) lanes and corridors across the United States highway network. The primary goals are to fix continuity gaps along continuous corridors, standardize restriction tagging, improve lane-level guidance, and ensure reliable routing data in OpenStreetMap.

Types of Activity

Our team will focus on adding, correcting, and refining HOV infrastructure data, specifically:

  • Fixing HOV Continuity: Closing gaps where hov=lanes or dedicated HOV ways temporarily drop off mid-corridor.

  • Tagging Validation: Verifying minimum occupancy tags (hov:minimum=) and time-based conditional access (hov:conditional=).

  • Geometry Refinement: Ensuring correct tagging for both physically separated HOV ways (highway=motorway + hov=designated) and integrated lane-level HOV configurations (hov:lanes=*), as well as mapping designated ingress/egress points and physical barrier restrictions.

We pay strict attention to local mapping conventions and aerial alignment. In cases where lane configurations or access rules are unclear from available imagery and compliant sources, we refrain from guessing and leave the segment unmapped or add a note for local contributors.

Geographical Scope and Timeframe

  • Geographical Scope: The project will take place in the United States.

  • Start Date: October 20, 2026.

  • Target Completion Date: End-November 2026 (approximately November 30, 2026).

  • Project Status: Active short-term organized editing sprint.

How to Find Edits

All edits made by our team within this project will use the dedicated hashtag #mapbox_hov.

Editing Team

All team members completed a thorough onboarding process before editing on OpenStreetMap and are fully familiar with OSM mapping principles, community guidelines, and organised editing guidelines.

The team primarily uses the iD Editor. New editors are guided to standard OSM training materials, including the OSM Wiki and internal validation guidelines.

Mapping Documentation and Guidelines

When mapping HOV lanes and access restrictions, the team follows standard OpenStreetMap documentation:

Sources

All mapping will strictly adhere to OpenStreetMap guidelines and licensing requirements. We will rely on the following sources to determine and verify lane counts, turn lanes, and HOV restrictions:

1. All available sources on the OpenStreetMap site itself:

1.1 Backgrounds or Satellite imagery: The latest available imagery based on capture dates in the editor background panel (e.g., Esri, Maxar, Bing).
1.2 Photo Overlays or Street-level sources: Open street-level imagery (Mapillary, Bing Streetside, etc.).
1.3 Overlays: Public OSM GPS traces, TIGER roads, etc.

2. Sources with ODbL license

3. Mapbox sources:

For cases where there is not enough ground truth data from OSM (Backgrounds, Overlays, etc.), we will use collected Mapbox telemetry data, GPS traces, and on-the-ground knowledge from test drivers to produce and verify the edit.
We are fully committed to transparency and are ready to share all sources used for mapping, as well as provide additional context whenever needed.

Quality Assurance and Clean-up

To ensure high data quality and prevent topology/routing errors (such as broken routing continuity, misaligned lane counts, or incorrect turn restrictions), edits undergo internal validation prior to and after uploading. Team members review history and local mapping patterns before making changes. Feedback from local OSM communities is monitored continuously.

Results

Progress reports and metric updates will be provided upon project completion at the beginning of December 2026 in our public repository ticket.

  • Metrics tracked: Number of changesets, corrected HOV road segments (km), and verified access/ingress points.
Contact

We strongly welcome feedback from local mappers, as local ground truth always prevails. If you have questions about a specific changeset, suggestions for process improvement, or local insights:

You can also find any relevant changeset using the #mapbox_hov tag and leave a comment directly.

Vorherrschende Sprache
JavaScript
Sterne
254
Forks
46
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus mapbox/mapping

Alle Issues in mapbox/mapping

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.