Api Feature Request: Expose Scheduled Stop Information For Upcoming Waypoints

Discussion in 'Suggestions' started by bart#2410, Oct 29, 2025 at 5:19 PM.

Tags:
  1. bart#2410

    bart#2410 New Member

    Joined:
    Oct 22, 2025
    Messages:
    3
    Likes Received:
    0
    Thank you for the API; it's a valuable tool.

    I am developing an application focused on generating additional announcements for existing DLC. To do this effectively, I need a reliable way to know which of the upcoming stations or markers are scheduled stops for the current service.

    Currently, while the API returns upcoming station and marker data, there is no flag to distinguish between a station the train is merely passing through and a station where the train must stop.

    Feature Request / Proposed Solutions:

    I'd like to request a feature to expose this "stop" or "pass" information.
    1. Preferred Solution: Add a Stop Flag: Could be a flag to the data structure for each station/marker in the relevant API endpoint. This would immediately enable accurate announcement creation.

    2. PIS Endpoint Fix: If this information is already intended to be available via the PIS system, please address the issue where many PIS endpoints are currently unusable due to invalid characters (like spaces) in the URLs. Fixing the PIS endpoints could be an alternative way to access the service's stopping pattern.
    Any additional endpoints are welcome too, for example to return aspects of the schedule, or simply the current scenario marker and it's location / distance.

    Thanks again, great work so far!
     

Share This Page