Various types of reach ID and HRU ID in network data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- data
Research direction
Start by reviewing how netCDF reach and HRU IDs are read and how the dev1.2_hru-id branch approaches the change. Trace the network topology augmentation path and determine the acceptance criteria for 32-bit integers, 64-bit integers, and strings while preserving internal 32-bit mapping.
Written by the indexing model from the issue text.
Description
Issue: currently allow only 32bit integer for river network ID.
ideal: allow 32bit, 64bit integer and string for IDs.
Possible solution: Create module to read IDs based on netCDF type and then generate dictionary (hash table) to map internal ID (which use 32bit integer) to these external IDs. use internal ID for network topology augmentation.
Plan to work on this dev1.2_hru-id branch
- Dominant language
- Fortran
- Stars
- 62
- Forks
- 73
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ESCOMP/mizuRoute
-
bug cesm-coupling cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
cesm-coupling enhancement infrastructure no answer change standalone
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
enhancement new features SUMMA coupling
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement infrastructure SUMMA coupling
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
infrastructure SUMMA coupling
Difficulty 5/5 Over a week Newbie friendliness 32/100
All issues in ESCOMP/mizuRoute
Similar issues
-
Add: ESP 2 PTOpencheck:passed feeds:add
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yt-project/yt#5624 ·
Maintainers usually reply within 1 day
-
automation missing-model model-sync provider:fireworks-ai
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/models.dev#12458 ·
Maintainers usually reply within 1 day
-
correction metadata
Difficulty 2/5 Under an hour Newbie friendliness 65/100
acl-org/acl-anthology#10753 · 1 comment ·
Maintainers usually reply within 1 day
-
Interactive node: valid JSON with mixed-type arrays (e.g. `[1, "a"]`) is rejectedPossibly taken @phil-opp claimed this today. Opendaemon rust
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day