For migration, PySTAC automatically migrates a catalog when you read it in. So if you were to read in a 0.8.1 catalog, normalize_and_save it to a new location, it should produce a 1.0.0-beta.2 catalog
you could also walk through all the children and items recursively (
catalog.walk()) and call .validate() on them to make sure they fit to spec. If there's any migration problems, that would be a bug and I'd love to hear about them
Thanks @lossyrob ! I'm in the process of bringing head of dev from last week into our system (it's bazel based, so things are a bit funky). I'll immediate update it to head as I see pystac/validation in the pull I just did. I'll give normalize_and_save this week. I see it here (noted for myself :) :
find . -name *.py | xargs grep normalize_and_save
./pystac/catalog.py: def normalize_and_save(self, root_href, catalog_type):
find . -name *.py | xargs grep normalize_and_save
./pystac/catalog.py: def normalize_and_save(self, root_href, catalog_type):
We have some custom (not pystac based) code that generates stac catalog files from our existing yaml catalog and it will be perfect to have a pystac generated version to compare against and 2 validators I can use to check. I was looking at stac-validator and was a bit bummed about how terse the verbose mode was. For my own understanding, I am considering writing a quick program that probes files based on my understand and prints what it finds and where things are not as expected. e.g. kinda like gdalinfo / ogrinfo but more linter focused and mostly about me learning.
The gdalinfo equivalent sounds interesting. This STAC sprint I'm going to be working on spinning up a CLI that can support a variety of utility methods that expose PySTAC functionality & beyond to the command line. A
stac info /path/to/catalog.json seems like a natural utility to add to that. Are you going to be at the STAC sprint, and want to touch base around potentially combining efforts on that?
@schwehr (and anyone else interested in the sprint): If you sign-up at https://groups.google.com/g/stac-sprint-6/ you'll be on the email updates about the sprint. And signing up on the general form at https://forms.gle/x27HJ1yfejSmHiZB6 will help me keep track of everyone.
And all info, including the schedule, should be posted at https://github.com/radiantearth/community-sprints/tree/master/08182020-remote/software
(I'm still working on it today - my sprint before the sprint ;) )
Would be great to have you join.
Good. And let's chat tomorrow, I have a couple of STAC browser questions to make this working: https://docs.google.com/document/d/1Dk4M0i0_LWWGHlMw4Xd0RRzWeWIXIRM4q_98qNBTV0w/edit#heading=h.o80u2yuzzrv8
i think this should be the official sprint logo
1 reply
@kbgg https://earth-search.aws.element84.com/v0.
The
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
1 reply
@matthewhanson @m-mohr @jbants @kbgg @lossyrob - I just added you all as contacts for the various 'rooms' as we discussed on the call today. See https://github.com/radiantearth/community-sprints/blob/master/08182020-remote/software/README.md#room-info Feel free to tweak it, particularly if you want to put the time you'll be there to kick it off.
And anyone else, feel free to add a room if you'd like some dedicated discussion time.
I think I may have written that before I realized it'd make sense to just have you in the main room.
And do I need to create a new Zoom on my University account or is there a way to do a breakout session from the Lobby we can link to?
I can make a zoom room for you. That'll be better, as it won't have a 40 minute limit.
It's on my list to make zoom rooms for all of them, but then I realized I should hurry up and post vs get everything perfect.
Let me make a validation one right now.
Okay, that sounds good., thanks.
And https://gitter.im/SpatioTemporal-Asset-Catalog/validation# should be up if you want to try and add that (I'll also get to it later)
If you have a chance could you try that zoom now? I scheduled it for tomorrow, I'm curious if the scheduled time matters.
@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.
Hi all, I'll start the general zoom room in about 30min, so everybody in non-American timezones is welcome to join! https://planet.zoom.us/j/93187144321
@m-mohr Is something like his useful for your catalog indexing?
https://docs.google.com/spreadsheets/d/1f-qpoGHohTdY9BVi9drb4mCRX8OLzZhlmKMJi9AEW20/edit#gid=0
https://docs.google.com/spreadsheets/d/1f-qpoGHohTdY9BVi9drb4mCRX8OLzZhlmKMJi9AEW20/edit#gid=0
Maybe open it for edit access? Currently, can only read