Skip to content

Develop HTML renderings for REST endpoints #55

Open

Description

@matthesrieke

Details to be defined (e.g. using Spring templates, ...)

Activity

  1. Govind9012 commented on May 8, 2023

    @Govind9012

    i want to handel this module , i have sufficient amount of knowledge to do this . i am a beginner in open source . just needed some guidence

  2. Swastik-123 commented on Sep 10, 2023

    @Swastik-123

    i can't find details can you tell me the root

  3. shreyashkumar01 commented on Dec 16, 2025

    @shreyashkumar01

    Dear @matthesrieke,
    I hope this message finds you well.
    I am writing to formally request assignment to the Helgoland repository issue: "Fix permalinks in trajectory view" (Issue #33). I see this as a high-impact task for improving the user experience, as the permalink function is currently reported as erroneous for trajectories, retaining a former time-series state.

    Technical Approach and Rationale

    My approach will focus on the front-end logic, which is built with Angular and TypeScript (based on previously provided Helgoland documentation).
    State Serialization Trace: I will investigate the component or service responsible for generating the permalink URL, specifically the function that serializes the current view state into URL query parameters.

    1. Trajectory State Validation: The core fix involves ensuring this function correctly distinguishes between a standard time-series view and a trajectory view, overriding the stale time-series parameters with the active trajectory's identifier and spatial/temporal bounds.

    2. Relevance to the 52°North Ecosystem
      Addressing this client-side state issue is vital for making the visualization of complex geo-data reliable. My awareness extends to the broader ecosystem, including projects like javaPS, which provides an interoperable processing framework for web applications.
      javaPS implements the OGC WPS specification, version 2.0.

    It is a full Java-based Open Source implementation built upon the arctic-sea project.
    Understanding how standardized OGC services handle geo-data processing, even on the backend (as with javaPS), strengthens my ability to ensure the Helgoland frontend correctly requests and serializes parameters for diverse observation data types (time series, trajectories).

    I am confident in my ability to implement and verify this fix efficiently. Please let me know if I can be assigned this issue.

    Thank you for your time and consideration.
    Best regards,
    shreyashkumar01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions