Does anyone have any 1.0.0 APIs I can test the QGIS plugin against?
@kbgghttps://earth-search.aws.element84.com/v0. The sentinel-s2-l2a-cogs collection is what you want. sentinel-s2-l1c and sentinel-s2-l2a are catalogs for the original JP2K files in eu-central-1 and are in requester pays buckets. But the COGs are free
If you have a chance could you try that zoom now? I scheduled it for tomorrow, I'm curious if the scheduled time matters.
Everything seems to work, thanks. Added to the GH page. Good night, see/hear you tomorrow.
@gilltk I notice in your posts from Oct 2019 you mentioned work with historic aerial photography (HAP) frames. I'm keen to know how this work has progressed, and whether your team implemented any additional properties for STAC items and collections related to HAP data? I'm currently looking at options to modernise search/discovery tools for an archive of ~1 million digitised HAP frames, ~300,000 satellite images, and ~2,000 digital aerial photography projects.
@jbants Yes, that's likely easier to fill than hidden in the Google Doc - and hopefully in some days we don't even need that any longer and can just use the STAC Catalog Index ;-)
Maybe open it for edit access? Currently, can only read
Yup, thanks for the catch. Should be open now
@lossyrob What's the relation between PySTAC and the Python Validator from @jbants ?
Hoping to figure that out this STAC sprint!
Yea, we had briefly chatted about it last sprint, but I'd like to get a solution this sprint. Most likely go with a pystac solution. We can chat more in the validation channel
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
@matthewhanson do you want us to @ you to be let in?
I've updated the document with the room infos for all new rooms...
Morning, still looking over all the ideas to see what make sense for me to help with (mostly python things)
@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