issue_comments: 272398208
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/1201#issuecomment-272398208 | https://api.github.com/repos/pydata/xarray/issues/1201 | 272398208 | MDEyOklzc3VlQ29tbWVudDI3MjM5ODIwOA== | 10050469 | 2017-01-13T09:26:05Z | 2017-01-13T09:26:05Z | MEMBER |
Yes, this is what I meant with xarray not being directly "cartopy aware". The reason is that xarray intends to be a general library, and tries to avoid defining too many keyword arguments in order to avoid confusion. However, xarray passes along any kw argument you want to the underlying mpl plot function (https://github.com/pydata/xarray/blob/master/xarray/plot/plot.py#L379). You'll have to catch it first, either from the |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
200364693 |