API mobiliteit.lu ATP

Name: API mobiliteit.lu
Creator: Administration des transports publics
License: https://creativecommons.org/licenses/by/4.0/
Keywords: api,arrets,depart,transport-mobilite,transport-public

Updated on March 10, 2022 — Creative Commons Attribution 4.0

Administration des transports publics

Administration compétente en matière de transports publics en ce qui concerne la gestion, l'organisation et le contrôle des services de transports publics réguliers et spécialisés. Plus particulièrement, l'administration est en charge de la gestion technique et financière des réseaux de transports…

4 datasets

Informations

License: Creative Commons Attribution 4.0
ID: 6048b5ee58974d5771b858e0

Temporality

Frequency: Real time
Creation date: March 10, 2021
Latest resource update: March 10, 2022

Participate

Add a reuse Contact the producer

Embed

<div data-udata-dataset="6048b5ee58974d5771b858e0"></div><script  src="https://staging.data.public.lu/static/oembed.js" async defer></script>

Permalink

Description

L'Administration des transports publics vous offre l’accès à son OpenAPI des départs en temps réel.

Définition du schéma de l'API (XSD)

Veuillez contacter opendata-api@verkeiersverbond.lu pour obtenir votre clé personnelle.

I) Arrêts des transports publics (location.nearbystops)

A) Vous devez indiquer les coordonnées géographiques x, y (en système WGS84):

originCoordLat=
originCoordLong=

B) Selon vos besoins vous pouvez préciser:

maxNo= un nombre max. d'arrêts retournés
r= un rayon autour des coordonnées (en mètres)

Exemple requête

https://cdt.hafas.de/opendata/apiserver/location.nearbystops?accessId=<API-KEY>&originCoordLong=6.09528&originCoordLat=49.77723&maxNo=5000&r=100000&format=json

(Remarque: Si vous voulez recevoir tous les arrêts existants utilisez les valeurs dans l'exemple)

II) Départs en temps réel (departureBoard)

Utilisez le résultat au-dessus. Cette liste vous indique l'identifiant de chaque arrêt. Vous avez besoin de cet identfiant pour générer les départs en temps-réel de l'arrêt souhaité.

id=

Exemple requête

https://cdt.hafas.de/opendata/apiserver/departureBoard?accessId=<API-KEY>&lang=fr&id=200426002&format=json

Files ²

API

departureBoard

Updated on March 10, 2022 — xml — 17 downloads

location.nearbystops

Updated on March 10, 2022 — xml — 7 downloads

API

departureBoard

Updated on March 10, 2022 — xml — 17 downloads

URL: https://cdt.hafas.de/opendata/apiserver/departureBoard?wadl
Permalink: https://staging.data.public.lu/en/datasets/r/9a0d38b5-5c59-4f10-9395-b3ef93d15713
Type: API
MIME Type: None
Created on: March 15, 2021
Modified on: March 10, 2022
Published on: March 15, 2021

location.nearbystops

Updated on March 10, 2022 — xml — 7 downloads

URL: https://cdt.hafas.de/opendata/apiserver/location.nearbystops?wadl
Permalink: https://staging.data.public.lu/en/datasets/r/529e1137-3ea0-4b95-ae54-8936e5fe3b70
Type: API
MIME Type: None
Created on: March 15, 2021
Modified on: March 10, 2022
Published on: March 15, 2021

Community resources ⁰

Publish a resource

You have built a more comprehensive database than those presented here? This is the time to share it!

No resources match your search.

Reuses ⁰

Add a reuse

Explore the reuses of this dataset.

Did you use this data ? Reference your work and increase your visibility.

Discussions ⁶

Discussion between the organization and the community about this dataset.

Sort by

API : Désactivation clé universelle / Universal key will be deactivated
Copy permalink
Administration des transports publics Customer Support
September 30, 2021
Attention : A partir du Lundi 18 Octobre, la clé universelle sera désactivée. Veuillez contacter opendata-api@verkeiersverbond.lu pour obtenir votre clé personnelle. Please note: From Monday, October 18, the universal key will be deactivated. Please contact opendata-api@verkeiersverbond.lu to obtain your personal private key.
La clé API universelle ne fonctionne plus
Copy permalink
JB M
August 20, 2021
La clé API "universelle" c2fb3438-45a4-48ff-9f5f-3546da29c6a9 ne fonctionne plus. Le message d'erreur retourné est "quota exceeded for c2fb3438-45a4-48ff-9f5f-3546da29c6a9 on departureBoard(QuotaStatus(apiKey=c2fb3438-45a4-48ff-9f5f-3546da29c6a9, type=HARD_QUOTA_EXCEEDED, timeUnit=MONTH, softQuota=2976000, hardQuota=3720000, requestCounter=5157385"
Marcos Correia
August 20, 2021
Good afternoon, I'm having the same issue: "quota exceeded for c2fb3438-45a4-48ff-9f5f-3546da29c6a9 on departureBoard(QuotaStatus(apiKey=c2fb3438-45a4-48ff-9f5f-3546da29c6a9, type=HARD_QUOTA_EXCEEDED, timeUnit=DAY, softQuota=200000, hardQuota=250000, requestCounter=408236))". I work for the app Citymapper, providing transit information worldwide, including in Luxembourg. It is possible to have a specific access id where the quota is much higher? If so, what are the procedures to obtain it? Thank you very much for you attention, Cheers Marcos from Citymapper
Quoata Exceeded
Copy permalink
Pit Schneider
August 19, 2021
Hello. The sample request for departureBoard always returns "quota exceeded for c2fb3438-45a4-48ff-9f5f-3546da29c6a9". Same thing happens when changing the "id" parameter. Is a different key necessary? If so, how can it be obtained? Thanks for your help!
JB M
August 20, 2021
Same problem here. The api key c2fb3438-45a4-48ff-9f5f-3546da29c6a9 does not work anymore. The error returned is quota exceeded for c2fb3438-45a4-48ff-9f5f-3546da29c6a9 on departureBoard(QuotaStatus(apiKey=c2fb3438-45a4-48ff-9f5f-3546da29c6a9, type=HARD_QUOTA_EXCEEDED, timeUnit=MONTH, softQuota=2976000, hardQuota=3720000, requestCounter=5157385
Administration des transports publics Customer Support
August 20, 2021
We are currently working on resolving this issue, we will post an update once the fix is in place.
New vs old
Copy permalink
Tom Harris
May 21, 2021
What are the main differences from the old API? Will the old one stay live? I noticed the new one is much slower to respond (e.g. the example get stops is ~7000ms vs 70ms on the old).
Tom Harris
May 21, 2021
Just noticed the example is pulling a large distance by default. Even then, changing to match the parameters from the old one it is around 150 ms.
Administration des transports publics Customer Support
May 25, 2021
Dear Tom, The old API will be switched off soon, so we recommend using the new one. The example provided does indeed request all our stops at once, so that explains why it takes a little bit longer to get the response. In general, both API’s can’t be directly compared, as they differ in the architecture as well as the content. The new API is based on the REST architecture and does provide much more information compared to the old one. For the location.nearbystops service, you will get addditional information about the different products / lines for a given stop .
no real time data?
Copy permalink
Jerry Kreins
May 1, 2021
Even with ?rtMode=FULL, the departureBoard doesn't seem to return any real time data (whilst the old API still does). Hasn't the realtime feature been enabled yet or do I miss a thing? Thanks for your help.
Administration des transports publics Customer Support
May 4, 2021
Could you please try again, the realtime data should be available now. Check for a field named “rtTime” in the response.
Jerry Kreins
May 5, 2021
Yes, it works now! Great! Thanks a lot! :-)