home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 258496425

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/pull/1024#issuecomment-258496425 https://api.github.com/repos/pydata/xarray/issues/1024 258496425 MDEyOklzc3VlQ29tbWVudDI1ODQ5NjQyNQ== 4160723 2016-11-04T17:29:54Z 2016-11-04T17:29:54Z MEMBER

Option D seems indeed the cleanest and safest option, but

Even eagerly loading indexes is potentially problematic, if loading the index values is expensive.

I can see use cases where this might happen. For example, It is common for 1, 2 or higher-dimension unstructured meshes that the coordinates x, y, z are arranged as 1-d arrays of length that equals the number of nodes (which can be very high!). See for example ugrid conventions.

I admit that currently xarray is perhaps not very suited for handling unstructured meshes, but IMO it has great potential (especially considering multi-index support) and I'd love to use it here.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  180451196
Powered by Datasette · Queries took 0.628ms · About: xarray-datasette