Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#74 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
api, cli

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Rust
Stelle
13
Fork
1
Merge medio
2g 4h
PR unite (30g)
66

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mapbox/mapbox-cli

Tutte le issue di mapbox/mapbox-cli

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.