Select data and name when pointing it chart with ggplotly

By -

I did everything in ggplot, and it was everything working well. Now I need it to show data when I point a datapoint. In this example, the model (to identify point), and the disp and wt ( data in axis). For this I added the shape (same shape, I do not actually want different shapes) to model data. and asked ggplot not to show shape in legend. Then I convert to plotly. I succeeded in showing the data when I point the circles, but now I am having problems with the leyend showing colors and shapes separated with a comma...

I did not wanted to make it again from scrach in plotly as I have no experience in plotly and this is part of a much larger shiny proyect, where the chart adjust automatically the axis scales and adds trend lines the the chart among other things (I did not include for symplicity) that I do not know how to do it in plotly.

Many thanks in advance. I have tryed a million ways for a couple of days now, and did not succeed.

# choose mtcars data and add rowname as column  as I want to link it to shapes in ggplot
data1 <- mtcars
data1$model <- rownames(mtcars)
# I turn cyl data to character as when charting it showed (Error: Continuous value supplied to discrete scale)
data1$cyl <- as.character(data1$cyl)

# linking colors with cylinders and shapes with models
ccolor <- c("#E57373","purple","green")
cylin <- c(6,4,8)  
# I actually do not want shapes to be different, only whant to show data of model when I point the data point. 
models <- data1$model
sshapes <- rep(16,length(models)) 



# I am going to chart, do not want leyend to show shape
graff <- ggplot(data1,aes(x=disp, y=wt,shape=model,col=cyl)) + 
  geom_point(size = 1) +
  ylab ("eje y") + xlab('eje x') +
  scale_color_manual(values= ccolor, breaks= cylin)+
  scale_shape_manual(values = sshapes, breaks = models)+
  guides(shape='none') # do not want shapes to show in leyend


graff

chart is fine, but when converting to ggplotly, I am having trouble with the legend

# chart is fine, but when converting to ggplotly, I am having trouble with the legend

graffPP <- ggplotly(graff)
graffPP

legend is not the same as it was in ggplot

I succeeded in showind the model and data from axis when I point a datapoint in the chart... but now I am having problems with the leyend....



from Recent Questions - Stack Overflow https://ift.tt/3fNSpC8
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more