Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    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
    Chris Holmes
    @cholmes
    Basically with GEE now you can take advantage of all their operations, combining multiple images, and then output the results as COG.
    So we can likely do some cool demo of some operations on GEE and then output and read the COG with cog-explorer / qgis / lambda tiler, etc.
    Fabian Schindler
    @constantinius
    That is awesome! (Of course, we'd love to do the ops in the browser)
    Chris Holmes
    @cholmes
    :) Me too... But Earth Engine has a lot of operations to catch up with...
    Fabian Schindler
    @constantinius
    Yep, indeed.
    Sorry, do you have control over that too? landsat-pds.s3.amazonaws.com
    Chris Holmes
    @cholmes
    no, not that one.
    Oh, and from before. I did email Joe F, but he didn't respond.
    Feel free to poke him again.
    Is the landsat-pds also needing the range option? How was it working before?
    Fabian Schindler
    @constantinius
    I don't know, it stopped working today, or yesterday
    Chris Holmes
    @cholmes
    Huh, that's weird.
    And it's just the CORS stuff that stopped working?
    Fabian Schindler
    @constantinius
    Yeah, @Schpidi did also poke him
    Yes
    Chris Holmes
    @cholmes
    super odd
    Seth Fitzsimmons
    @mojodna
    joe was on vacation last week; i'm not sure when he gets back
    Chris Holmes
    @cholmes
    Chris Holmes
    @cholmes
    Matt said he turned on cors on google cloud.
    Chris Holmes
    @cholmes
    Looks like it's working, but I'm getting weird technicolor versions
    https___geotiffjs_github_io_cog-explorer__long_-121_997_lat_37_540_zoom_8_scene_https___storage_googleapis_com_mdh-test_SanFranciscoS2BGRN_tif.png
    but I'm now getting the same with the aws ones:
    Banners_and_Alerts_and_https___geotiffjs_github_io_cog-explorer__long_-95_354_lat_28_969_zoom_13_scene_https___s3-us-west-2_amazonaws_com_planet-disaster-data_hurricane-harvey_SkySat_Freeport_s03_20170831T162740Z3_tif.png
    Chris Holmes
    @cholmes
    Ok, cors should be enabled in my google bucket now! Matt got his working, and told me how to do it in mine. Looks like the Range thing was needed, and then options seemed to work? Unless trying it out directly in cog-explorer isn't a full test... I don't think I have a cors plugin installed.
    Fabian Schindler
    @constantinius
    Hi @cholmes
    Sorry, I'm already home (its 9:30 here).
    Its great to hear you managed to get it to run, good job!
    I inspected the SanFranciscoS2BGRN.tif case. Theres two things: 1) The default contrast correction is way off as the image seems to be in a good contrast already by itself. I'm working on this issue (as it currently affects all RGB images). 2) if this image originates from Sentinel 2, then bands are a bit odd. In the gdalinfo it displays the band description as B2, B3, B4, B5 (which is actually Blue, Green, Red and Near Infrared) so the colors are quite odd indeed.
    The second image has the same contrast issue. If you click on the wrench in the upper right and delete the 'sigmoidal' step, then the image should be quite normal. The default settings originate from a version where we thought only Landsat 8 images will be displayed.