Skip to content

Sense for a remote .ome.tiff #875

@yarikoptic

Description

@yarikoptic

I arrived at https://avivator.gehlenborglab.org/ and was excited to try out on our data in dandiarchive. Eg. see https://dandiarchive.org/dandiset/000026/draft/files?location=sub-I38%2Fses-SPIM%2Fmicr&page=1 and there for any relevant file click on blue "i" to get to metadata which would have URLs under

    "contentUrl": [
        "https://api.dandiarchive.org/api/assets/3fec7df4-e31c-4327-979f-330a6c84eaec/download/",
        "https://dandiarchive.s3.amazonaws.com/blobs/7ab/b62/7abb6225-a8a8-46e3-8f54-3643c333c5f1"
    ],

where API one would potentially mint a URL (with mimetype provided in the header IIRC) or just redirect to S3 one below, but would require our CORS policy to be adjusted first. So I have tried a direct url to S3: https://avivator.gehlenborglab.org/?image_url=https://dandiarchive.s3.amazonaws.com/blobs/7ab/b62/7abb6225-a8a8-46e3-8f54-3643c333c5f1 but it errorred out with console showing only attempts to treat it as zarr prefix:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions