Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#74 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
api, cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Rust
Estrellas
13
Forks
1
Merge medio
2 d 4 h
PR fusionados (30 d)
66

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de mapbox/mapbox-cli

Todos los issues de mapbox/mapbox-cli

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.