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

[FEATURE]: Allow fitbounds to use only a subset of traces

Abierto
  • ¿Algo no está bien?
#8,076 3 comentarios 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
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
data-visualization

Línea de trabajo

Start by tracing how scattergeo handles layout.geo.fitbounds and gathers locations, then read the linked discussion in issue #8046. Define how a trace-selection option should work while keeping unselected routes visible, and verify the selected-route extent, including antimeridian-crossing routes, without changing the broader view.

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

Descripción

enhancement feature P3 size: 3

Summary

I would like to request a way to control which traces participate in the fitbounds calculation.

The current behavior is correct in the sense that fitbounds considers all relevant traces in the graph. However, for interactive maps with multiple routes, it would be useful to fit the view to a selected trace (or subset of traces) while keeping the other traces visible.

Related issue

This feature request follows from the discussion in the closed issue:

plotly/plotly.js#8046

More specifically, this follows from camdecoster's comment on #8046.

Use case

I am building an interactive flight-route map using scattergeo.

The map contains many flight routes. When the user selects one route, I would like to:

  1. Keep all routes visible.
  2. Fit/zoom the map to the selected route only.
  3. Keep the other routes visible, but exclude them from the calculation used to determine the fitted view.

This is particularly important for routes crossing the antimeridian.

For example, a route from Vancouver (YVR) to Seoul (ICN) crosses the antimeridian. If this is the only trace in the graph, fitbounds: 'locations' correctly fits the route and rotates the map to the Pacific.

However, when all the other routes are present, fitbounds considers their locations as well, resulting in a much wider/global view.

Current workaround

I tried temporarily removing the other routes, fitting the map to the selected route, and then adding the other routes back.

The first two steps work correctly:

  1. Remove/disable the other routes.
  2. Fit the view to the selected route.

However, as soon as the other routes are added back, fitbounds recalculates using all traces and the view immediately returns to the wider extent.

I also tried making the other routes transparent, but opacity does not exclude their locations from the fitbounds calculation.

I therefore currently have to choose between fitting the map correctly to the selected route and keeping all routes in the graph.

Proposed feature

It would be useful to have a way to specify which traces should participate in the fitbounds calculation.

For example, conceptually something like:

layout: {
    geo: {
        fitbounds: 'locations',
        fitbounds_traces: [3, 7]
    }
}
Lenguaje dominante
JavaScript
Estrellas
18.3k
Forks
2k
Merge medio
1 d 19 h
PR fusionados (30 d)
21

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 plotly/plotly.js

Todos los issues de plotly/plotly.js

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.