Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • airGRiwrm airGRiwrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

La forge institutionnelle d'INRAE étant en production depuis le 10 juin 2025, nous vous invitons à y créer vos nouveaux projets.

  • IN-WOP
  • airGRiwrmairGRiwrm
  • Issues
  • #1
Closed
Open
Issue created May 19, 2020 by Dorchies David@david.dorchiesOwner

Database structuration

The network configuration should contains:

  • the list of hydraulic nodes of the system: locations where inflows and outflows occur. Each point has at least an unique identifier. Description fields and geomatic information could be added in the future.
  • the nature of the point: run-off or flow
  • as we assume that the network is only constituted with confluences, the identifier of the next downstream hydraulic node should be provided.

For hydraulic nodes of nature "run-off", we need some more informations:

  • area of the water basin
  • the hydrological model used

Times series:

  • need to be stored in one matrix containing each time step in lines and all fields in columns in accordance with tidyverse specifications.
  • a vector with the timestamps should be associated with the data (in a list?).

Proposition of structuration in a list with:

  • an entry date containing the vector of timestamps
  • one entry for each hydraulic node identified by the id of the node with a matrix containing all associated data.
Assignee
Assign to
Time tracking