What is this?

This project visualizes all trips in your city's Nextbike network. Each trip is inferred from bike availability data collected every minute.

How is the data collected?

The data is updated every minute. A bike is recorded as part of a trip if it disappears from the dataset and reappears at a different location later. The route is calculated by connecting these points using OpenStreetMap's bike network.

Why do some trips look wrong?

Some trips may seem unrealistic due to GPS inaccuracies, faulty time data, or route calculation errors. For example:

• 1-minute trips: These could be due to delayed data updates or an error on Nextbike's part.
• Weird routes: OpenStreetMap may not always provide the shortest or most realistic path, especially in pedestrianized areas.

Why don't you remove incorrect trips?

Filtering "incorrect" trips is tricky. Some 1-minute trips are valid, like short hops between stations. Sometimes the trips are valid, but the time data didn't update. Deleting those trips based on general rules removes real data.

Where is my city?

This is a sample visualization for the cities of Giessen and Marburg.

You want your city analysed?

Make it happen: get someone with technical knowledge to set up tracking for your city's Nextbike network by following the instructions in the Nextbike City Analysis Project.

The project uses open data from Nextbike and OpenStreetMap, making it easy to expand to new locations.

Where do you get the data from?

Nextbike's publicly available data endpoint.
The endpoint for the city of Giessen.

Looks cool - can I use this?

Sure. It's public for a reason. Either link to this page, or for people with technical knowledge, to the Nextbike City Analysis Project.