Chris Holmes

> I don't think this would get rid of the need for that class, as the the CQL intersects geometry class is composable with other predicates through the logical operators,...

> For cases where the request is sent as a JSON document in the body, it should be GeoJSON. For cases where the request is a GET request and intersects...

> So, in short, I think I support @cholmes idea ... although I think that middle level of capability, the one that sits between CORE and CQL should be a...

Yup. And to emphasize the key point: Even should try to implement client support for 1., using https://app.swaggerhub.com/apis/cportele/lika-nrw/0.0.1 And @pvretano will post his implementation here when it's up. Having that...

@rouault - gotcha. I talked to @cportele and he said he'd try to update it, but he's got a lot going on. Will update this ticket if it gets done.

+1 on this in general. Though I just remembered that POST on `/items` I believe is taken by the transaction (which makes sense). In STAC we use it on the...

Ah, interesting. Didn't realize POST could work that day - you learn something new every day :) I suppose we'll charge ahead in STAC, but would be great to have...

Cool. For now in STAC we just have top-level /search And will probably stick with that as it makes describing it simpler: implement Features API, and add the /search endpoint....

Cool, great to hear that's on the radar too. The other more advanced query thing I'd love to see is aggregation. Planet has done bits of that in our custom...

I definitely would prefer virtual collections that require some description of what they can handle to an endpoint that takes collectionIds parameter. I do think an /all endpoint could make...