intake / intake/intake-thredds

how to handle url's which aren't xarray friendly

Open
#24 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
11
Forks
7
PR merge metrics
No merged PRs in 30d

Description

This came recently as I was struggling to open a url using xarray. Goes back to https://github.com/pydata/xarray/issues/2233; https://github.com/pydata/xarray/issues/2368

@rsignell-usgs suggested using NetCDF4 https://stackoverflow.com/a/66247797/6046019

Just an FYI. Not sure if it will cause a headache here.

Contributor guide

Open the contributing guide

Research direction

The report names no file, test, or specific behavior to change; begin by reviewing the linked xarray issues and the NetCDF4 suggestion to establish the expected URL handling. A maintainer would need to clarify the affected intake-thredds entry point and define a reproducible URL case and acceptance criteria before work can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.