Matthew Hanson

Ok that makes sense. It would be nice to have something a bit more transparent...like some assets may have an s3 URL and some may not. Here's an updated example:...

Yeah, I sorta do still agree with myself, but not super strongly. It just seems like a the wrong place to make such distinction. The spec isn't really clear that...

Put some more thought into what a `create_derived_item()` function should do. Parameters: - `items`: an array of items - `id`: an new ID must be provided - `collection`: a collection,...

These are some great features, some random thoughts: - For referencing assets by spectral band "common_name" I filed https://github.com/stac-utils/pystac/issues/275 - being able to include multiple files with different CRS's would...

This is great addition, thanks @TomAugspurger . I agree with the thoughts here. I see an ItemCollection as the main entity that most downstream applications would consume, as it's the...

If data_type is provided that's great, but if not, I think the asset should be queried for it's data type. It would be a shame if the `file` extension is...

@DanSchoppe Good idea, I'll look into setting up an email list for announcements and such. Thanks!

This is a bit more complicated, since the record would have to be published, then the new record received and published. Probably a better way to do this, perhaps trigger...

Note this could have impact to various stactools submodules that may be using these functions.

I hadn't really thought about this before @lossyrob brought it up, and just always thought that inclusive makes the most sense, as I (and probably most people) think in terms...