issue_comments: 457907278
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/1475#issuecomment-457907278 | https://api.github.com/repos/pydata/xarray/issues/1475 | 457907278 | MDEyOklzc3VlQ29tbWVudDQ1NzkwNzI3OA== | 1197350 | 2019-01-27T10:49:07Z | 2019-01-27T10:49:19Z | MEMBER |
N is the number of cells. M is the number of points required to specify the cell vertices, e.g. 4 for 2D quadmesh, 3 for 2D trimesh, 8 for 3D quadmesh, etc. Regarding your options 1 or 2, I guess I'm agnostic as to how it is implemented. I recognize 2 introduces lots of complications. What matters is how it will interact the indexes, i.e. can we easily select data based on cell bounds? I will have to take some time to think about what you wrote, as it is hard for my brain... 🙃 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
242181620 |