Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Vincent Sarago
    @vincentsarago
    well we implemented our own solution for mosaic so I’m not sure
    @davidraleigh so you are talking about radiantearth/stac-spec#150
    this is another topic as issue 807
    I need to catch up but was there any other discussion about mosaic ?
    Chris Holmes
    @cholmes
    Thinking about min/max zoom - I was tempted to 'support' other projections, like have a field that defaults to web mercator, but that lets you supply something else. But thinking about it you'd always want to have web mercator, since the STAC Item won't know what projection the tile service might want to serve it in, and most do web mercator.
    If a dynamic tile service wanted to supply an alternate projection would it be reasonable for it to figure out the zoom levels it supports from the web mercator ones?
    Vincent Sarago
    @vincentsarago
    yes
    (that’s how we do, plus it’s only informative)
    Chris Holmes
    @cholmes
    Cool. Because the alternatives all sound pretty bad to me (an array of objects of potential projections + zoom levels?)
    Vincent Sarago
    @vincentsarago
    :thumbsup:
    Chris Holmes
    @cholmes
    Is there a reference somewhere on Float, Int, Complex?
    What is 'complex'? And are there other options beyond those 3?
    Vincent Sarago
    @vincentsarago
    numpy data type
    Chris Holmes
    @cholmes
    Like we should support any of https://numpy.org/doc/stable/user/basics.types.html ?
    Kyle Barron
    @kylebarron
    I would've expected just C types
    Vincent Sarago
    @vincentsarago
    https://github.com/mapbox/rasterio/blob/master/rasterio/dtypes.py#L26-L59
    Those are the ones supported by gdal/rasterio
    Chris Holmes
    @cholmes
    Cool. Thinking of just listing those as the options...
    Kyle Barron
    @kylebarron
    I'd expect a standard list of available type names?
    Chris Holmes
    @cholmes
    Yeah, that makes the most sense to me.
    Should I just use the list from rasterio?
    Vincent Sarago
    @vincentsarago
    int
    int8
    int16
    int32
    int64
    uint
    uint8
    uint16
    uint32
    uint64
    float
    float32
    float64
    complex64
    complex128
    Chris Holmes
    @cholmes
    Looks to be: ''UInt16', 'Int16', UInt32',Int32','Float32','Float64','CInt16', 'CInt32','CFloat32','CFloat64'
    Vincent Sarago
    @vincentsarago
    or yours
    Chris Holmes
    @cholmes
    Any preference? I tend to like uncapitalized, so I think maybe slight preference for yours. Do we need the un-numbered and 8 ones?
    Kyle Barron
    @kylebarron
    I wouldn't think we'd need unnumbered? Those just add a degree of complexity?
    Vincent Sarago
    @vincentsarago

    I wouldn't think we'd need unnumbered?

    but it can gives you an idea of the range …

    oh I agree
    we need numbered
    ;-)
    Kyle Barron
    @kylebarron
    int normally just refers to int16 or int32 I think?
    yes of course we need numbered :)
    Chris Holmes
    @cholmes
    Ok, so leave those out.
    Vincent Sarago
    @vincentsarago
    int is int16 I think
    Chris Holmes
    @cholmes
    And we need the 8's? My list was just from looking at https://github.com/mapbox/rasterio/blob/master/rasterio/dtypes.py#L26-L59 which didn't have the 8's
    Kyle Barron
    @kylebarron
    We definitely need at least uint8? Because simple RGB PNGs for visualization are in uint8
    byte is uint8
    From the rasterio list
    Chris Holmes
    @cholmes
    gotcha
    byte is a good name for us to use too?
    Kyle Barron
    @kylebarron
    I think int8 is very uncommon, but maybe it exists?
    Chris Holmes
    @cholmes
    Ok, I'll take a crack at the list. May have things wrong, but can discuss in a PR
    Chris Holmes
    @cholmes
    @matthewhanson & @vincentsarago - just put in an idea around the single band stuff: radiantearth/stac-spec#807
    Chris Holmes
    @cholmes
    Thinking about the name some - tiling is such an overloaded word in geospatial. Wondering about something like 'Rendering Hints'. Since it seems like these fields would be useful to anyone rendering the data, not just dynamic tilers?
    Chris Holmes
    @cholmes
    @vincentsarago / @kylebarron ^ would 'rendering hints' make sense as the name?
    Vincent Sarago
    @vincentsarago
    yes
    Chris Holmes
    @cholmes
    @/all - ok, got a draft-y PR up. See radiantearth/stac-spec#879
    Review is much appreciated, as I feel like I'm flying a bit blind since I don't make dynamic tilers and so don't really know all the details of the fields.
    More information to give people context would be great.
    After you all look it over I can try to make the example and json schema.