Skip to content

React-App for searching, visualising and downloading data on Swiss lakes. Consists of a Web GIS for comparing raster and point datasets, Data Portal for selecting products and extensive options for graphing and downloading the products.

active 2025-04-162026-05-19 (UTC)

Complete coverage26,458 / 26,458 hourly files (100%) · 2 absent upstream2023-08-152026-08-21 (UTC)
Events
97
Pushes
34
Pull requests
1
Issues
31
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 399 days from 2025-04-16 to 2026-05-19. Pushes: 34 total, peak 3 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 31 total, peak 6 in a day. Comments: 20 total, peak 7 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
ymarcon443207
hsolleder24004
charlottegiseleweil7001
npasche1001

Recent activity

Latest issues, pull requests and releases

  • Issue#34hsolleder2025-12-15 12:15
    refactor: combine events.csv modifications to avoid conflicts
  • Issue#34hsolleder2025-12-15 12:15
    refactor: combine events.csv modifications to avoid conflicts
  • Issue#33hsolleder2025-12-15 10:39
    chore: mirror GitLab issues to GitHub
  • Issue#6hsolleder2025-12-15 10:23
    [FEAT] visualization of corrected data
  • Issue#31ymarcon2025-11-06 12:44
    bug: github issues management
  • Issue#23hsolleder2025-09-01 08:28
    [FEAT] Data curator and advisor roles are stored
  • Issue comment#19hsolleder2025-08-31 17:35
    [FEAT] Data expert is periodically notified of QA/QC submissions to review
  • Issue#19hsolleder2025-08-31 17:35
    [FEAT] Data expert is periodically notified of QA/QC submissions to review
  • Pull request#29ymarcon2025-07-24 14:00
  • Issue comment#17hsolleder2025-07-14 12:46
    [FEAT] Integrate LéXPLORE metadata into pipeline
  • Issue comment#5charlottegiseleweil2025-07-14 11:47
    [FEAT] QA JSON
  • Issue comment#19ymarcon2025-07-14 10:56
    [FEAT] Data expert is periodically notified of QA/QC submissions to review
  • Issue#7ymarcon2025-07-07 08:59
    [FEAT] Visualize removed/flagged/reviewed data based on metadata
  • Issue#8ymarcon2025-07-07 08:59
    [FEAT] Let user select data to be flagged via shape drawing
  • Issue#16ymarcon2025-07-07 08:58
    [FEAT] Explore the possibility to authenticate maintainers with Renku's gitlab
  • Issue#23hsolleder2025-06-27 05:56
    [FEAT] Data curator and advisor roles are stored
  • Issue#22hsolleder2025-06-26 14:18
    [FEAT] Store user submission in database
  • Issue#21hsolleder2025-06-26 14:07
    [FEAT] Provide access to user view via URL
  • Issue#20hsolleder2025-06-26 13:57
    [FEAT] Data expert can (in)validate user submission in Datalakes
  • Issue#19hsolleder2025-06-26 13:49
    Data expert is periodically notified of QA/QC submissions to review
  • Issue#18hsolleder2025-06-16 08:16
    Metadata resulting from the quality assessment (L0 to L1) should be part of the pipeline
  • Issue comment#14hsolleder2025-06-16 07:46
    [FEAT] Integrate metadata throughout the data pipeline
  • Issue comment#16ymarcon2025-05-22 15:08
    [FEAT] Explore the possibility to authenticate maintainers with Renku's gitlab
  • Issue comment#16ymarcon2025-05-21 16:52
    [FEAT] Explore the possibility to authenticate maintainers with Renku's gitlab
  • Issue#16ymarcon2025-05-21 09:01
    [FEAT] Explore the possibility to authenticate maintainers with Renku's gitlab

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.