DatosBizi
Español

How to read the data

Methodology and data quality of Bizi in Zaragoza

We explain where the data comes from, when it is updated and what the figures you see mean. We also point out which metrics are estimates and how to interpret them with care.

238 days of coverage276 stations with historyHealthy

Primary source

Bizi Zaragoza GBFS

The official Bizi system, which we query and review regularly.

Visible coverage

238 days · 03/03/2026, 01:00:00 -> 02/11/2026, 06:05:56

It is the same base that feeds reports, lists and station sheets.

Observed cadence

~2 min per poll

Pace observed in recent collections.

Active versions

cov-20261102-41853515 · API v0.5.0

Latest published report: November 2026.

Where the data comes from

From the official system to information that is useful to you

We start from the official Bizi Zaragoza system. We collect the state of each station, check that the data is consistent and group it to show current availability, history, districts, monthly reports and the API. GBFS is the technical format used by that official source.

Current state

What is there now

Available bikes, free docks and capacity show the last known state of a station; they are not a historical average.

History summary

What usually happens

Movement, hours without bikes or docks, time-of-day patterns and district comparisons use many samples, not a single snapshot.

Activity and mobility

Measures to compare

The activity index is used to compare activity between stations or areas. It is not the official number of trips.

Prediction

A hint, not a guarantee

Predictions combine past patterns and the recent state to warn about possible problems in the short term. Always check the real state before you set out.

Visible FAQs

Questions that change the interpretation the most

Where does the station data come from?

The main source is the official GBFS feed of Bizi Zaragoza: https://zaragoza.publicbikesystem.net/customer/gbfs/v2/gbfs.json. From that discovery file, station_information and station_status are queried periodically, then validated and aggregated for analytics.

How often is the dashboard updated?

Data is refreshed periodically and the API uses a short cache to avoid overloading queries. That is why there can be a few minutes of difference between one view and another.

Does demand mean the real number of trips?

Not exactly. It is an index that measures system activity (the activity index). It works well for comparing days and areas, but it should not be read as an official count of completed trips.

What exactly are the dashboard predictions?

They are estimated values of future availability (for example +30 and +60 min). They are calculated from past patterns and the current situation. They help anticipate, not confirm with 100% certainty what will happen.