helgasoft

Here is one way of getting the data through _sf_. ```r library(sf) fname

Previous example is with **polylines**. This one - with filled **polygons**. Tooltips show each polygon's name which is a county name from the _sf_ shape data. ```r library(sf) fname

Implemented in latest echarty v.1.5.6.02. Check new command **?ec.util**. See also [more code and demo clip](https://helgasoft.github.io/echarty/gallery.html#leaflet). ```r library(sf); library(echarty) fname

related to #52

@liuyu322, maybe you borrowed from the [example code](https://echarts.apache.org/examples/en/editor.html?c=map3d-wood-city)? I don't think you need _buildings.json_. Data is huge and probable reason for your performance issue.  Here is the code updated...

Could be a performance issue. [Here](https://stackoverflow.com/questions/25219352/webgl-scene-doest-render-because-of-lost-context/25219582#25219582) is an explanation. Or it could be browser GC (garbage collection) kicking in after that much idle time.

scatter3D highlighting would be nice indeed. But even more important are actions [select](https://echarts.apache.org/en/api.html#action.select) and unselect, and event [selectchanged](https://echarts.apache.org/en/api.html#events.selectchanged). Then we'll have truly interactive 3D charts !

...but does it make sense? Do you have a use-case when _nameRotate_ will improve somehow the 3D scene rendering?

yes, see your point

Update v.5.3.0 - indeed _data.itemStyle.borderWidth_ does not work. Only **color** and **opacity** are working inside _data.itemStyle_. _series.itemStyle_ supports all of them.