Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Chris Holmes
    @cholmes
    Do they work for GET?
    Stephan Meißl
    @Schpidi
    I'm confused, the google links seems to work now for me
    https://geotiffjs.github.io/cog-explorer/#long=-93.976&lat=30.015&zoom=12&scene=https://storage.googleapis.com/pdd-stac/disasters/hurricane-harvey/0831/SkySat_PortArthur_s02_20170831T195425Z.tif
    Chris Holmes
    @cholmes
    Oh yeah, forgot to respond to the jpeg encoded stuff too. Yes, totally awesome work! And I too hope we'll be able to get funding that can help 'cover' it.
    Fabian Schindler
    @constantinius
    Sounds good
    Stephan Meißl
    @Schpidi
    maybe a delay in the configuration?
    Fabian Schindler
    @constantinius
    still not working for me
    Chris Holmes
    @cholmes
    Maybe? Except I configured that a day or two ago...
    Fabian Schindler
    @constantinius
    CORS plugin enabled? ;)

    Do they work for GET?

    Yes

    AFAICT google still does not include the correct headers in the OPTIONS response
    Chris Holmes
    @cholmes
    Ok, I have a potential way for us to get help on this :)
    My friend Matt leads google earth engine dev, and they recently started outputting COG's...
    And he just gave me an example to test: https://storage.googleapis.com/mdh-test/SanFranciscoS2BGRN.tif
    Stephan Meißl
    @Schpidi
    yes, GET seems to work. so the CORS plugin is only needed for the OPTIONS request. from there on it works. sorry for the noise
    Chris Holmes
    @cholmes
    So hopefully he can get it working...
    Fabian Schindler
    @constantinius
    Ah, I'll try right away
    btw: about this image http://oin-hotosm.s3.amazonaws.com/56f9b5a963ebf4bc00074e70/0/56f9c2d42b67227a79b4faec.tif
    Now that we know how, do we know someone that can set the headers there too?
    Chris Holmes
    @cholmes
    though I'll try to bash around a bit more.
    @mojodna - do you have powers to set CORS headers on the OIN bucket?
    Fabian Schindler
    @constantinius
    https://storage.googleapis.com/mdh-test/SanFranciscoS2BGRN.tif has the same issue.
    Seth Fitzsimmons
    @mojodna
    i do
    looking now
    Chris Holmes
    @cholmes
    oh yeah, I was pretty sure it would. But if I rope Matt in about this he has access to all the google people. Instead of me just searching around online.
    Fabian Schindler
    @constantinius
    I see, now I understand
    Seth Fitzsimmons
    @mojodna
    current CORS configuration:
    <!-- Sample policy -->
<CORSConfiguration>
    <CORSRule>
        <AllowedOrigin>*</AllowedOrigin>
        <AllowedMethod>GET</AllowedMethod>
        <MaxAgeSeconds>3000</MaxAgeSeconds>
        <AllowedHeader>Authorization</AllowedHeader>
    </CORSRule>
</CORSConfiguration>
    err, maybe that was a sample
    Chris Holmes
    @cholmes
    I did: <CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <AllowedHeader>Range</AllowedHeader>
    (I think the sample just becomes the default when you enable it)
    Seth Fitzsimmons
    @mojodna
    ah, Range. makes sense
    Chris Holmes
    @cholmes
    Not sure if HEAD is actually needed
    Range seemed to be the magic incantation
    Seth Fitzsimmons
    @mojodna
    updated
    Fabian Schindler
    @constantinius
    Okay, it works if you use https:
    https://geotiffjs.github.io/cog-explorer/#long=168.457&lat=-17.554&zoom=16&scene=https://oin-hotosm.s3.amazonaws.com/56f9b5a963ebf4bc00074e70/0/56f9c2d42b67227a79b4faec.tif
    We have some strange artifacts in JPEG images on the border ...
    Thanks @mojodna
    Seth Fitzsimmons
    @mojodna
    that's "normal" (i want to get to the bottom of those, but they're in the overviews)
    whoa, awesome!
    Chris Holmes
    @cholmes
    sweet!
    Why do you need to use https: ?
    Fabian Schindler
    @constantinius
    Also a security issue. Browsers do not let you send unsecure requests from a secure origin, I think I can recall

    that's "normal" (i want to get to the bottom of those, but they're in the overviews)

    Ah, so no issue with the decoding, good to know

    Seth Fitzsimmons
    @mojodna
    no need to use HTTPS for S3, but i think those are the URLs that published in the catalog...
    Stephan Meißl
    @Schpidi
    usually you get a mixed origin warning
    Chris Holmes
    @cholmes
    Ok, psyched we got at least one working.
    I've got to shower and eat breakfast and get in to the office
    Fabian Schindler
    @constantinius
    Okay, do that
    Chris Holmes
    @cholmes
    But I'll see if I can try out some more google cloud configurations.
    Fabian Schindler
    @constantinius
    I think you've earned it :)
    Chris Holmes
    @cholmes
    And I want to get that Sentinel image on s3
    Fabian Schindler
    @constantinius
    Yeah, that'd be great