Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#74 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
58/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
api, cli

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Rust
Étoiles
15
Forks
2
Merge moyen
2 j 4 h
PR mergées (30 j)
66

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de mapbox/mapbox-cli

Toutes les issues de mapbox/mapbox-cli

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.