Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent display of Zahnradbahn stops (web and app) #863

Open
stadtnavimanager opened this issue Dec 19, 2024 · 2 comments
Open

Inconsistent display of Zahnradbahn stops (web and app) #863

stadtnavimanager opened this issue Dec 19, 2024 · 2 comments
Assignees

Comments

@stadtnavimanager
Copy link
Collaborator

Description:

The stops for the Zahnradbahn are inconsistently displayed between the web version and the app:

  • In the web version, Zahnradbahn stops are always shown, even when the Public Transport (ÖPNV) filter is disabled.

    • Suggestion: Zahnradbahn stops could appear under the Subway Stations filter. Alternatively, a dedicated filter for Zahnradbahn stops could be created.
  • In the mobile app, Zahnradbahn stops are not displayed at all, regardless of filter settings.


Steps to reproduce:

  1. Open stadtnavi in the web version and the mobile app.
  2. Search for an area with Zahnradbahn stops: this is between Degerloch and Stuttgart Süd
  3. Toggle the Public Transport (ÖPNV) and Subway Stations filters and observe the behaviour.

Observed behavior:

  • Web version: Zahnradbahn stops are always visible, even when relevant filters are disabled.
  • App: Zahnradbahn stops are not visible at all.

Expected behavior:

  • Zahnradbahn stops should be displayed consistently across both platforms.
  • They should be controlled by an appropriate filter:
    • Option 1: Include them under the existing Subway Stations filter.
    • Option 2: Create a dedicated filter for Zahnradbahn stops.

Screenshot Webversion:

Image


Additional information:

A consistent and logical display of Zahnradbahn stops will improve the user experience and ensure that all transport options are easily accessible across platforms.

@github-project-automation github-project-automation bot moved this to To do in stadtnavi Dec 19, 2024
@stadtnavimanager stadtnavimanager moved this from To do to Backlog in stadtnavi Dec 19, 2024
@hbruch
Copy link

hbruch commented Jan 21, 2025

For web, this is fixed (see screenshot). However, the layer funicular is not yet defined in the POI-Layers sheet, so it's position in the layer switcher might be inappropriate. @stadtnavimanager , could you check please? Pesonally, I'd rank train and subway higher than bus and funicular

Image

@stadtnavimanager
Copy link
Collaborator Author

Thanks @hbruch !
I adjusted the positions in the POI-Layer and added funicular and rackrailway:

Image
You think it is okay like this?

Can you please also check the following issue?
#804

I'd like to have consistent names and translations in the settings and the layers.

  • In the settings, the names are still wrong (it only says Seilbahn, Zahnradbahn is missing)
  • I translated Zahnradbahn with "rack railway" (this is what I researched back then - not sure if it is the most common translation, do you know?

Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

2 participants