Issue with NA handling in scatter plots: Two NAs per category cause incorrect line connection
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- R
- Sterne
- 2.7k
- Forks
- 641
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Issue Summary
When using plot_ly() in R with a scatter plot (mode = "lines+markers"), missing (NA) values are expected to create gaps in the line plot. However, if exactly two NA values exist per category, the missing values are incorrectly connected by a line instead of creating a gap.
Interestingly, when the hovertemplate is removed, the line plot behaves as expected (i.e., creating a gap for NA values). This issue only occurs when there are exactly two NA values per category; the code works with any other number of NA values.
Additional Discovery:
The issue is resolved if I include the argument split = ~Category, but I cannot find documentation for split in Plotly, which makes me think it may be deprecated. Moreover, when the hovertemplate is removed, the inclusion of split does not work as expected and does not resolve the issue.
Reproducible Example
The following R code demonstrates the issue:
library(plotly)
df <- data.frame(
Category = rep(c("A", "B"), each = 6),
Date = c(2020, 2021, 2022, 2023, 2024, 2025, 2020, 2021, 2022, 2023, 2024, 2025),
Value = c(10, 15, NA, NA, 20, 25, 12, 14, NA, 22, NA, 27)
)
df$Date <- factor(df$Date, levels = unique(df$Date), ordered = TRUE)
plot_ly(
df,
x = ~Date,
y = ~Value,
color = ~Category,
type = 'scatter',
mode = 'lines+markers',
text = ~Category,
hovertemplate = paste0("Date: %{x}<br>Category: %{text}")
)
Expected Behaviour
- NA values should create a gap in the line plot, i.e., they should not be connected.
- This works correctly when there is any number of NA values other than exactly two in any category.
Actual Behavior
- When there are exactly two NA values per category, the missing values are incorrectly connected by a line instead of creating a gap.
- When the hovertemplate is removed, the lines create a gap as expected.
- The issue only arises when there are exactly two NA values per category; any other instance of NA works fine.
- Including split = ~Category resolves the issue, but:
- I cannot find any Plotly documentation on split, leading me to believe it may be deprecated.
- Interestingly, when the hovertemplate is removed, including split does not resolve the issue.
Additional Notes
This seems to be an issue specifically triggered by the combination of NA handling and the hovertemplate. I would appreciate further insight on why this happens or suggestions for a workaround to preserve the gap in the case of two NA values.
System Info
R version 4.4.2 (2024-10-31 ucrt)
Platform: x86_64-w64-mingw32/x64
Running under: Windows Server 2019 x64 (build 19045)
Matrix products: default
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginnen Sie damit, das reproduzierbare plot_ly()-Beispiel im Issue auszuführen, und vergleichen Sie die Ausgabe mit und ohne hovertemplate und split = ~Category. Verfolgen Sie, wie der R-Aufruf von plotly NA-Werte und Kategorie-Traces darstellt, und überprüfen Sie anschließend, dass genau zwei NAs pro Kategorie eine sichtbare Lücke erzeugen, ohne split zu benötigen oder hovertemplate zu entfernen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- r
- Bereich
- data-visualization
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100