some markers do not show the full KEY value on event_data() for plotly_click

[ahsanshah]

I am testing the event_data() functionality to show the KEY value for a marker add_trace to ggplotly.

I noticed that while it works fine for most points that I select/over/lasso....it only shows the first CHARACTER for some of the points. It seems unusual why it is doing this.

I am using the code based on the following example: https://github.com/ropensci/plotly/blob/f1900cc3cd464408a60ffadfe3e95460747430e0/inst/examples/plotlyEvents/app.R

Any idea?

[cpsievert]

Hmm, I can't seem to replicate this, can you provide a reproducible example?

[ahsanshah]

I am not able to replicate in a very simple example (such as the mtcars one we have). However, in my case this is an add_trace on top of a ggplotly geom within a Shiny Reactive. Also, the EVENTS are generated withing dynamically as an API call via JSONlite.

I can try to send you a minimal example but need to put one together. Would Shiny/Reactive behave any differently per my environment.

Also, How do we CONTROL what columns are returned by EVENT_DATA? The default values (curve number, point number) are not needed for me. Is there any documentation on what EVENT_DATA returns and how we can control the output or add new columns?

[timelyportfolio]

Without a reproducible example, I am having a hard time fully understanding what you are trying to get? These lines control the event data that is sent, so lines send curveNumber, pointNumber, x, and y. Then these lines add z and key if available. There does not currently appear to be an opportunity for customization.

I'm sure @cpsievert would be happy to explore adding this functionality or if not, I am happy to tackle. An example would give me most of what I need to get started.

[ahsanshah]

This one is weird. I am not sure if it helps to send my entire app.r 600+ line code. I cannot reproduce a minimal example.

However, What it seems like is that if i use a STATIC DATAFRAME, it does not have any issues with the MARKER values. However, if I use a dynamic Shiny Reactive as an input, it does not capture the Markers for the event names.

[timelyportfolio]

Thanks, I should be able to look at this on Sunday also unless someone beats me to it.

[cpsievert]

You can't currently control what variable(s) are returned by event_data(), although you can always subset according to your needs.

Also, your problems are probably due to the fact that data and key are the same object in your example?

[ahsanshah]

It doesnt look like h"key" and "data" being the same is the issue. As I said, if i use a static dataframe (with key and data being the same), it works fine. When I use a Reactive input (which I need to do) and set the data to be a full data frame and the key to be a specific column, it seems to result in a few "markers" not returning the proper values. I am wondering how I can troubleshoot this. As you can see below, it works for 9 markers and fails for 5. Note that ALL 14 have a valid KEY value but it does not reflect that in the event_data() output for V5. In other words, using plotly_click or plotly_hover..the event_data() does not properly capture the marker values for a subset of the markers. I cannot see any data anomalies with these specific markers at all.

I am still going to try to see how I can minimize a reproduceable example but any thoughts are appreciated. Also, as suggested, I have subset the event_data() output and merged it with a second data frame to control the output. Thanks for that suggestion.

[timelyportfolio]

I tried a couple different ways to reproduce in Shiny with no luck. When you say "I cannot see any data anomalies with these specific markers", is that on the R or the JavaScript side? I would say that @cpsievert's suggestion to subset is better practice with or without Plotly. Please let me know if you come up with something reproducible.

[cpsievert]

Closing until someone can come up with a reproducible example.

[ahsanshah]

I believe I have a reproducible case which illustrate this. Attached is an app.R file and a RDS file to show the issue.

Here is a screenshot of the behavior. I have tested this across various data sets. For some reason, a subset of the markers do NOT show the correct KEY value for the EVENT_DATA. It is the same behavor for CLICK, HOVER, or SELECT/DRAG. To show the example, I am using HOVER.

Looking at the data frame, these 2 items have valid KEY values (e.g. event.id in my case)

Here are the files. Let me know if you have questions. If this is indeed an issue, please reopen the case.

Support.zip

[cpsievert]

You seem to have global vars floating around in that app, for instance, what is test2?

[ahsanshah]

test2 is the dataset used for the geom_smooth in the ggplot prior to conversion to PLOTLY. I have reuploaded the files with the test2.RDS. I need both (geom_smooth) and ATLevents (Markers) on the plot. However, I want the event_data to be based on the markers.

Let me know if you can reproduce this on your end.

Support.zip

[mauritzvdworm]

I have noticed a similar issue using the event_data() function applied to a plotly image created from a reactive data frame. No problem with a static data frame though. In my case I have some data by county that I plot on a choropleth (map). I want to add some additional information when you click on a specific country. When the data frame is filtered and the plot redone the "plotly_click" does not select the correct points.