Categorization of public transport network

Open data API in a single place

Provided by Stadt Graz - Verkehrsplanung

Get early access to Categorization of public transport network API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.09.19 10:30
Created
2025.09.19
Available languages
English
Keywords
Verkehr, Studie, ÖV-Netz, Art. 20 Abs. 5 B-VG
Quality scoring

Dataset description

The Graz city area is accessed by numerous bus and tram lines with different service quality. The different qualities of the individual lines are grouped into categories in relation to the serviced stops in order to obtain a clear overview of the public transport quality. In addition, the stops are also categorized according to ÖROK on the basis of Austria-wide public transport quality classes and both categorizations are compared with each other. This should serve as a decision-making aid for urban planning and transport planning on future urban developments or developments. The result can be compared with that of previous years in order to be able to see where improvements have been implemented on the one hand and where there is a need for action for public transport development on the other. Publication of studies, reports and surveys pursuant to Article 20(5) of the B-VG Type: study Contractor:in: Prime Mobility & Consulting Costs: € 13.896 Institution: Councillor
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks