Add Navigation API support: Directions, Matrix, and Isochrone
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
- 66/100
Línea de trabajo
Start with the command-generation flow and the vendored specs in openapi/ and custom-openapi/, then compare the linked Mapbox Directions, Matrix, and Isochrone API documentation. Done means the three Navigation API command groups are represented by vendored specs and generated CLI commands can expose their route, matrix, and reachability operations.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Request
Add command groups for the Mapbox Navigation APIs — Directions, Matrix, and Isochrone — so an agent can compute routes, travel-time matrices, and reachability from the terminal.
Why
These answer questions a frontier model fundamentally can't, because they depend on the live road network and traffic:
- Directions — route, distance, and traffic-aware travel time between points. "How long to drive from A to B right now, and which way."
- Matrix — travel times/distances across many origins and destinations at once. "Of these 10 candidates, which is fastest to reach from the office." This is the real "travel time between places" primitive.
- Isochrone — the area reachable within N minutes. "What's within a 15-minute walk." Natural pair with search-along-route and site-selection workflows.
Each produces concrete, checkable output an agent can act on, and none of it is memorizable.
Context
The CLI generates commands from the OpenAPI specs vendored in openapi/ and custom-openapi/. None of the Navigation APIs are vendored today, so the commands don't exist. The README notes upcoming releases will extend coverage to most public APIs — this is a request to prioritize the Navigation three.
- Lenguaje dominante
- Rust
- Estrellas
- 15
- Forks
- 2
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 66
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de mapbox/mapbox-cli
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 58/100
mapbox/mapbox-cli#74 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
mapbox/mapbox-cli#30 ·
Los mantenedores suelen responder en 1 día
Todos los issues de mapbox/mapbox-cli
Issues similares
-
area: compat area: parsing bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
reubeno/brush#1526 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
OFN writer emits `DocIRI` as a bare IRI, which becomes a version IRI or a parse error on re-readAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
phillord/horned-owl#338 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
stackabletech/operator-rs#1301 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
jmcnamara/rust_xlsxwriter#205 · 4 comentarios ·