Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alex Kirk
    @a-kirk
    QQ RE sortby in place of sort stac-api extension: Do we expect this naming change to be stable? I do see sortby in some OGC docs, which I assume was the reason for the change, but I wanted to confirm that no further adjustments are expected for the extension name. (I apologize to the folks on Monday's call when I asked the same question).
    James Santucci
    @jisantuc
    :wave: i'm taking a stab at converting the label extension into usable Scala code. i have a question about some missing required fields where i'm not sure if fields aren't required as an oversight or if some strange objects are technically valid, specifically with label overviews objects. label:overviews is an optional list of Label Overview objects. Label Overview objects have three optional fields. does this mean that [{}, {}, {}] is a valid label:overviews property? relatedly, what purpose could someone have in providing a Label Overview object without a property key, or with a name property key and without the other fields?
    James Santucci
    @jisantuc
    in a similar vein, label:properties is actually of type [string] | null, not [string | null], right? in the case of a raster label, the value should be null, not [null]?
    Matthias Mohr
    @m-mohr
    @matthewhanson Question regarding common names in EO: https://github.com/radiantearth/stac-spec/tree/master/extensions/eo#common-band-names
    There are ranges that cover two common names (e.g. 0.6 is both green and red). So which to use? I guess the second value is exclusive?
    Matthew Hanson
    @matthewhanson
    They aren’t hard limits…greeen will have a band that starts at 0.5 and ends at 0.6, whereas red starts at roughly 0.6 and goes to 0.7
    yellow sort of cross between those two
    Michael Smith
    @hgs-msmith
    @m-mohr, I briefed on the OGC info Monday, I think @matthewhanson captured the info in the minutes. To answer your question: As a member, you should request to join the group as an observer. Once that's done, you should start getting meeting invitations.
    Matthias Mohr
    @m-mohr
    Thank you @hgs-msmith - I can't find Commons on the list of observable groups, unfortunately. I guess I'll contact OGC staff directly.
    Chris Holmes
    @cholmes
    I just put up an attempt at 0.9.0 version of Planet data - at https://storage.googleapis.com/pdd-stac/disasters-0.9.0/catalog.json Would be great if clients could check it out. Or if you want me to try your client to test let me know.
    Will change it over to be the main one once stac browser supports 0.9.0, so I don't break planet.stac.cloud
    Matthias Mohr
    @m-mohr
    @cholmes It seems all the links are broken inside the catalog file.
    Chris Holmes
    @cholmes
    @m-mohr - thanks for the catch, looks like I uploaded the wrong 'root' catalog. Attempting to fix now, but getting weird caching issues with google cloud storage.
    Matthias Mohr
    @m-mohr
    @cholmes Works for me now
    Matthias Mohr
    @m-mohr
    @cholmes Some comments:
    Chris Holmes
    @cholmes
    Thanks for the awesome feedback @m-mohr
    • stac_extensions - thanks for the catch. Was updating too many files at once by hand (some day I'll figure out pystac or something). We're actually get traction at Planet to implement a real STAC API and define an official Planet mapping, so I'll push for a schema at that point. But things are going to shift from mine.
    • roles for mosaic - you mean at the asset level? I think I need to update for 'roles' for all of them, not just the mosaic. Or you mean provider role?
    Chris Holmes
    @cholmes
    • eo:bands - yeah, that one is complicated to do 'right' with planetscope, as our satellites have a range of band widths, as they've evolved. But I suppose for my limited subset it should be easier, so I'll take a crack at it.
    • On the stac_extensions - I wasn't sure if that was supposed to be the extensions that are used in the items in the collection, or just the extensions used directly in the collection file. I'll fix it (and will try to check we make that clear, but I just looked at one example and didn't fully read the spec).
    Chris Holmes
    @cholmes
    • I can make some summaries for you :) I do like the summaries. Where's your STAC catalog again so I can use it for examples?
    Matthias Mohr
    @m-mohr
    • roles for mosaic: Yes, asset level, e.g. roles = data
    • From reading the documentation the stac_extensions thing should be clear, it's pretty long actually. Of course, you won't understand it just from examples...
    • summaries: Great! :-) Again, best is to read the docs and check the examples there. Just from examples you can't make good summaries IMHO. ;-) Here's our catalog, although it's generated automatically from Googles STAC 0.6.2 catalog and thus may not be the best example: https://earthengine.openeo.org/v1.0/collections Google is working on an updated version and other openEO implementers also still need to catch up in the next weeks.
    Chris Holmes
    @cholmes
    Thinking about adding a 'role' for usable data mask / qa band. Anybody have opinions on what to call it? 'udm'? 'qa_mask'? Others?
    (Need to do it for Planet data, and seems like a nice one to generalize)
    Matthew Hanson
    @matthewhanson
    I think qa or quality would be sufficient
    Chris Holmes
    @cholmes
    Does sentinel call it quality too? What does DG do? Quality to me always sounds like it's about pixel errors, not about identifying clouds, etc.
    Hamed Alemohammad
    @HamedAlemo_twitter
    Sentinel-2 has pixel-based cloud mask in L2A that is under QI_DATA and pixel-based classification (including bad pixel, and no-data labels) in L1C under IMG_DATA
    Chris Holmes
    @cholmes
    Hey all, for the call tomorrow would people be able to do a half hour or hour earlier? With no childcare my wife and I have to schedule our workdays so one of us is always on, and it turns out she has a really important meeting at the same time.
    If we can't meet earlier then I can try to join for the first 15 minutes or so...
    @matthewhanson - if that does work could you move the invite up a bit?
    Sorry for the attempted last minute switch - shelter at home with a 1.5 year old has been a challenge.
    Matthias Mohr
    @m-mohr
    I'm fine with any time...
    Chris Holmes
    @cholmes
    @/all Ok, I'll start in 17 minutes for anyone who can join (will see if we can just join Matt's standing meeting, if not I'll start a zoom), and then I'll have to drop off at 8, when we may pick up others.
    Chris Holmes
    @cholmes
    Ok, I'm on zoom: https://planet.zoom.us/j/8171436529 Meeting ID: 817 143 6529 If anyone wants to join and catch up.
    James and Josh are on.
    Matthias Mohr
    @m-mohr
    Struggling with Zoom...
    Chris Holmes
    @cholmes
    We'll start check in soon...
    Matthew Hanson
    @matthewhanson
    Just saw this
    joining zoom
    Alex Kirk
    @a-kirk
    doing a stand up but will try to join soon
    James Banting
    @jbants
    Can I get some feedback on this preliminary catalog
    https://geobase-spot-staging.s3.amazonaws.com/catalog.json
    Matthias Mohr
    @m-mohr
    @jbants Don't add null to stac_extensions (example)
    Also, version is not a core field, so better add "version" to stac_extensions.
    James Banting
    @jbants
    Thanks @m-mohr
    Chris Holmes
    @cholmes
    Hey @matthewhanson - asked Frank about Planet using shape + gdal affine transform like in the grid extension, and he said that plus epsg code would work for us and be a general solution. I should check with ESRI to be 100% sure it works for them too, as they were the advocates for our offset_x and offset_y.
    Now that I understand what the extension is actually for I feel like it could perhaps use tweaks in name / explanation. Based on the PR alone I had no idea it solved the same use case as Planet's offset / rows/cols fields. Should make it clear that it enables virtual catalogs / data cubes to fully populate without having to open the files.
    Tom Kralidis
    @tomkralidis

    Hi all: I hope everyone is keeping safe/well during this time. A bit of a pygeoapi / STAC update (since our November 2019 sprint in DC). I’m implementing STAC for realtime weather/numerical weather prediction data (i.e. GRIB2 data), and have a MVP.

    During implementation, I ran into #198 again. Are there any guidances on how to name the object ids? Having a difficult time coming up with something meaningful

    Matthias Mohr
    @m-mohr
    @tomkralidis Not a guidance, but I'm simply using the file names (assuming the files are all in the same folder and thus don't have conflicts)
    Matthew Hanson
    @matthewhanson
    I’m of the general opinion that a Collection should have similar Asset keys across all Items in that Collection.
    This allows users to look at a Collection and see which Asset keys they are interested in then use that Key when getting individual items.
    So, if your items all have a primary data file for instance call it the same thing across all items.
    Matthias Mohr
    @m-mohr
    @matthewhanson True, in my case it always a single item ;-)
    Tom Kralidis
    @tomkralidis
    thanks as always for the feedback guys