The individual zoom rooms don’t seem to work, as it says the host is still running another session (the main lobby one).
So I’m starting a Google Meet for STAC API Talk: https://meet.google.com/xrn-yhwy-pcb
So I’m starting a Google Meet for STAC API Talk: https://meet.google.com/xrn-yhwy-pcb
@lossyrob I'll be focusing mostly on API related things but one thing we discussed in our STAC tech meetups with Azavea is how we should manage typing going forward. PyStac has a rich type description set but I know you've been dealing with the multiple inheritance extension issue for validation. Because DevSeed has been doing a ton of FastAPI related projects lately we are all starting to get Pydantic focused and will probably use https://github.com/arturo-ai/stac-pydantic for a lot of base work going forward. What are you thinking is the best way forward to have a canonical Python typing and validation suite that we use both in PyStac and other projects that are not dealing directly with Catalog and Collection manipulation.
For validation, I just recently added a feature that validates against the JSON schemas (docs). I figure using the community-maintained JSON schemas is the best thing to validate against, since it will be the canonical way to validate across all languages. Not sure about the typing question though; what do you imagine are the typing needs?
I see the appeal of pydantic models if your just looking for domain models of STAC without the functionality for reading/manipulating/writing, so see stac-pydantic as a nice compliment. As much as we can share functionality of course would be great for de-duplication, open to suggestions there
I wonder if something like https://pydantic-docs.helpmanual.io/datamodel_code_generator/ could be used to make sure that the pydantic models are generated (and/or extended) directly from the "official" json schemas
The individual zoom rooms don’t seem to work, as it says the host is still running another session (the main lobby one).
So I’m starting a Google Meet for STAC API Talk: https://meet.google.com/xrn-yhwy-pcb
seems like the zoom breakout rooms aren't working; I also started a google meet for the python room
@sharkinsspatial Also for the multiple extension typing issue: this is how I worked around that; considering extensions as separate types that modify the stac object instead of inheriting from the core object types.
Interested in your thoughts on what sort of suite you mentioned should look like.
Python does have multi-inheritance, but it becomes a combinatorially explosive problem when you need to account for all extensions/requires dynamic extension at runtime that is hard to account for. So the solution that we put in place is to ditch extension inheritance for extension composition.
27 replies
Please try to update the room info at https://github.com/radiantearth/community-sprints/blob/master/08182020-remote/software/README.md#room-info
for all posted above
I think I'm going to just use the main room for the intro session. As it's just me and Matt on right now.
If anyone wants to an overview of the spec or to ask more intro questions join me at https://planet.zoom.us/j/93187144321 (I'm just using the main zoom room, since apparently I can't start more than one zoom meeting at once from my account)
The 27 reply thread above now has its own room: https://gitter.im/SpatioTemporal-Asset-Catalog/dynamic-tiling
Discussion of radiantearth/stac-spec#807
and other topics around making on the fly tile services from STAC catalogs.
What is the result of radiantearth/stac-spec#741 ? it has a
1.0.0-beta.3 milestone; so what are the thoughts about having items that belong to multiple collections?
@pomadchin I don't think there's a solution yet. The issue with multiple "parent" collections is that items can inherit some data from Collections (Item Assets) and then it's not clear how to resolve conflicts and multi-inheritance in general is always more complex than you usually like it to be.
i’m checking in for the day and checking out for the night. i had major headaches with some IDE issues for the majority of the day, but once resolved, was able to get the STAC GeoTools store working for assets on S3. it can render any image in a stac collection by passing in the item ID. i will be working on expading to support any http endpoint and enabling COG support tomorrow.
I was in the main lobby
Then let's meet in the main lobby.
That was before we ditched all those rooms.
@m-mohr will be in main lobby for a bit going through stac-api-spec issues:
https://planet.zoom.us/j/93187144321
@m-mohr will be in main lobby for a bit going through stac-api-spec issues:
https://planet.zoom.us/j/93187144321