Julia Signell

For this sprint I am planning to add a little tutorial notebook that explains how to read an asset into an xarray object using xpystac.

I have been mulling over what would be the most discoverable and ergonomic way to give access to read methods and I am strongly leaning towards creating an [xarray assets...

Hmm I was just looking over the 2.0 milestone and came across this. The file names in pystac seem to come from the extension repo names: - https://github.com/stac-extensions/pointcloud - https://github.com/stac-extensions/file...

It would make sense to me to pull this json blob in on release and then package it up as part of pystac. If that sounds like a reasonable approach...

I am wondering if it would be more ergonomic to have a method like `set_derived_from`. So you would create the new item using `Item(...` and then do `item.set_derived_from(original_item)`. It could...

I'm going to start work on a PR to add a `.set_derived_from` method to `pystac.Item`

It is a little hard to map these back to the current state of the tests, but I am fairly confident that all the cases listed in the original description...

I've been messing around with the interface from objects to extensions (#1051) and I think that if we change the invocation, option 2 becomes a little more attractive. In that...

yeah I think that's right. We can go ahead and close this.

I would expect `axes()` to return a list containing: - `df.index` (which is a `dask.dataframe Index`) - `df.columns` (which is a `pandas Index`)