LouisPauchet/UNIS_SvalbardWeatherInformation

Frontend V2

Open

#67 opened on Jun 24, 2025

View on GitHub
 (1 comment) (0 reactions) (2 assignees)Python (1 fork)auto 404
V1.1frontendhelp wanted

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

This issue is the biggest part of the V1.1. The idea is to rebuild the front end to facilitate further development.

For the version 1.1 - sandpiper, the following feature are planned to be transferred :

Map Page

Map and Layers

  • Map display with layer
  • Layer opacity control
  • Layer order control*
  • Layer category
  • Legend

Tools

  • GPX Import / Export
  • Map PDF Export*
  • Drawing Tools (tracks, dot, shapes...)
  • Measuring tools (Area, Distance, Distance from track)
  • Elevation profile*
  • Drawing feature management (selection, organisation...)
  • Geocoding place name

Weather station control

  • Weather Station
  • Wind Arrow
  • Information Popup basic
  • Information Popup restyled*
  • Project grouping
  • Station and project ON/OFF
  • Link to display time series

Time Series Page

  • Station selection
  • Variable selection
  • Multivariable selection
  • Multistation selection
  • Download Option (NC / CSV)

Credit page

  • Credits for fixed stations (per projects)
  • Credits for mobiles stations (per projects)
  • Credits for map layers
  • About
  • Disclaimer
  • Licence
  • Contributors

The features marked with * are new for this versions.

In the long term, we are thinking to include option to let user to upload terrain observations with logging mechanism, possibility to add observation a bit like in Varsom, maybe link information from varsom as well as sharing tracks.

Contributor guide

Research direction
Start by examining the current frontend codebase to understand its structure. Focus on completing the Map Page checklist items (e.g., layer order control, legend). Use the existing map display as a reference for implementing these features.
Tech stack
None
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40