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

Add Places API (Details) support: photos, busyness, and stable place IDs

Offen
  • Stimmt etwas nicht?
#74 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
api, cli

Rechercherichtung

Start by reading the existing mapbox search forward and search category command implementations, especially how they expose mapbox_id. Then review the Mapbox Places Details API material linked in the request and determine the response shape for the proposed command. Done means a mapbox places details <mapbox_id> command returns photos, busyness, business attributes, and stable place IDs.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement

Request

Add a command group for the Mapbox Places API — specifically the Details endpoint — so the CLI can return the enriched per-POI data that a coding agent can't get anywhere else: photos, busyness/popularity, business attributes, and stable place IDs.

Why

The CLI's headline pitch is giving an agent knowledge it doesn't have. Today the richest thing search returns is open hours, phone, and website — good, but the data that's genuinely unique to Mapbox lives behind the Places API and isn't reachable:

  • Photos — high-quality photos via direct URLs (per the blog). An agent could render or link a place's photo.
  • Busyness — a 0–100 activity score by hour and day of week. An agent could answer "is it busy right now" or chart the week's curve. Nothing else in the CLI exposes this, and no frontier model has it.
  • Business attributes — cuisine, accessibility, seating, Wi-Fi, entrance vs. vehicle arrival points.
  • Stable place IDs — persistent UUID anchors that survive data updates, so saved references don't break.

These are the demos that actually show the CLI's value. Geocoding a known address doesn't — the models already have it.

How it fits what's already here

The loop is half-built. mapbox search forward / search category already return a mapbox_id on every feature. The Places Details endpoint (public preview) takes exactly that mapbox_id and returns the enriched record. So this is a natural next command, e.g.:

# today: Search Box returns the id
mapbox search forward --q "Blue Bottle Coffee" --proximity -122.4194,37.7749 --limit 1
# -> properties.mapbox_id = "dXJuOm1ieHBvaToxZTM5YzE5Ny0..."

# proposed: Places Details enriches it
mapbox places details dXJuOm1ieHBvaToxZTM5YzE5Ny0...
# -> photos[], busyness, attributes, stable id
Vorherrschende Sprache
Rust
Sterne
15
Forks
2
Ø Merge
2 T. 4 Std.
Gemergte PRs (30 T.)
66

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/mapbox-cli

Alle Issues in mapbox/mapbox-cli

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

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