Rejseplanen template

[ds-bellcom]

When we try to use the "Rejseplanen" template, no options are retrieved under "Vælg stoppested" (in English: Select stop). How can this be and how can we fix this?

[tuj]

You need an API-key from rejseplanen's api. This should be set in the admin config:
https://github.com/os2display/display-admin-client/blob/develop/public/example_config.json#L6
In infrastructure:
https://github.com/os2display/display-admin-client/blob/develop/infrastructure/itkdev/etc/confd/templates/config.tmpl#L6

[ds-bellcom]

Thanks for the answer @tuj.

Can you also answer which API I should request access to in order to get this API key? I found this page (https://labs.rejseplanen.dk/hc/da/requests/new?ticket_form_id=17536468593565) and here I can choose between "API 2.0", "GTFS" and "Stoppestedsdata". Which one(s) should we request access to?

Maybe it's in the documentation, if so I haven't been able to find out where.

[sinejespersen]

API 2.0

[ds-bellcom]

Thank you very much @sinejespersen. We have now requested access - hopefully we will get access soon.

[ds-bellcom]

We have now received a response from Rejseplanen and they write the following (in Danish):

Jeg har kigget lidt på den integration OS2display har til Rejseplanen.
De bruger faktisk kun vores API til at finde holdeplads-ID, som de så genererer en afgangstavle for, via vores afgangstavle-software.

Jeg har skrevet til dem for at anbefale, at de implementerer én API-nøgle, så hver bruger ikke skal have sin egen.
Indtil da får du her en API-nøgle til testformål, med en kvote på 50.000 kald per måned:
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Have any of you received a request from Rejseplanen about this?

As I read it, there is supposed to be only one API key for OS2display (regardless of which municipality/supplier hosts the solution). I think it is a key that OS2 stores and distributes to the customers who are connected to the product community. Is that correct?

@agnetemoos @sinejespersen @tuj

[ChatBotBerg]

@agnetemoos & @turegjorup would you be so kind to ensurethat we get the sufficient background informaiton forthe coordination committee in to evaluate the risk and issues related to sharing an API , as well as get a plan for solving the problem.

[turegjorup]

@ds-bellcom we have recieved the same message via email from OS2. We will reach out to Rejseplanen next week to try to resolve this. It seems they have misunderstood the the self hosting aspect of the project. The current implementation was developed after advice from them in 2021.

[agnetemoos]

It would be reckless to distribute a Rejseplanen API key with the product. There is no way OS2 can control that the key is not abused in some way.

[turegjorup]

@ChatBotBerg The current "rejseplan" template enables the setup of slides showing what Rejseplanen calls "Afgangstavler", to do this your installation needs to be configured with a valid API key for accessing the Rejseplanen API. Back in 2021 we (ITK Dev) reached out to Rejseplanen Labs before developing the tempalte/feature. The current implementation is based on their advice.

It seems that the current service owner is not aware that OS2display is designed to be self hosted. His email only makes sense if for SAAS sofware with just one installation.

He also states that "Vi vil gerne hjælpe jer med at finde en ny løsning, når vi lukker vores gamle afgangstavle-software." The tempalte dependes on their "adgangstavle" feature.

We need to:

1. Re-open the dialog to figure out why they now consider our implementation to be "non optimal"
2. Migrate to another Rejseplan service if/when they close down "Afgangstavler" or loose the ability to show rejseplanen info in OS2display

I will do a follow up with Rejseplanen next week (Uge 27).

[ds-bellcom]

Thanks for the quick feedback. It sounds good that you, @turegjorup, will reach out to Rejseplanen so that we can get clarity on how it should work in the future.

And I completely agree - it doesn't sound like an optimal solution of everyone having to use the same API key, but that's what Rejseplanen itself suggested.

[turegjorup]

I have sent an email to Rejseplanen Labs asking for clarification on the issues they raise and for documentation and time frame on any new "Adgangstavle software"

I agree with @agnetemoos that we cannot distrbute an API-key with an Open Source system. I also don't think we can distribute their static data with the application given that you have to request access to the data.

I have also asked Rejseplanen Labs to clarify their statement recommendation that

... de implementerer én API-nøgle, så hver bruger ikke skal have sin egen.

Given that they explicitly state that

Hvis du som leverandør skal bruge Rejseplanens API på vegne af en kunde, er det din kunde, som skal anmode om adgang.

See: https://labs.rejseplanen.dk/hc/da/articles/21553113674909-Adgang-til-data-fra-Labs

[ds-bellcom]

We completely agree with you @turegjorup.

We have asked our customers to fill out the form on the Rejseplanen webpage so they can each receive an API key.

[turegjorup]

I have not heard back from Rejseplanen in regards to the problems they have raised. I have written today (Aug. 19) to them again to ask for a reply.