Breaking Changes
Die von MobiData BW angebotenen Schnittstellen und Datenformate werden stetig weiterentwickelt. Hier möchten wir auf die Breaking Changes hinwiesen und diese erläutern - wobei unser Changelog auf Github die ausführliche und vollständige Dokumentation aller Anpassungen bereithält. Die jeweiligen API-Dokumentationen enthalten stets den aktuellen Stand.
Geplante Änderungen
Geplante Breaking Changes, die in Zukunft anstehen, versehen mit einem groben Zeitpunkt.
GeoServer (WMS/WFS/WMTS/WCS)▶
Einstiegsseite des GeoServer.
| 2026Q1 | Layer werden eingestellt: MobiData-BW:park-api_car_buildings, MobiData-BW:park-api_car_on-street und MobiData-BW:park-api_item |
Umgesetzte Änderungen
Umgesetzte bzw. produktiv gegangene Breaking Changes mit Verlinkung in den Changelog-Eintrag aus dem Repository.
Lamassu (Sharing)▶
Endpunkte von GBFS 2.3 und GBFS 3.0.
| 2026-01-28 | rename lime_stuttgart to lime_bw (contains Stuttgart, Konstanz) |
| 2026-01-07 | remove dott_winterthur feed |
| 2025-12-19 | remove deer feed |
| 2025-12-15 | remove coono feed |
| 2025-11-26 | remove gmuend_bewegt feed |
| 2025-03-26 | Bump to the 2025-03-19 release, which
|
| 2024-07-09 | GBFS-Feed:
|
| 2024-05-07 | Upgrade Lamassu to version 2024-04-29T06-37. This i.e. solves feed subscription issues on startup (entur/lamassu#442) and a metrics issue (see entur/lamassu#439). Note: some metrics changed with this release, so monitoring/alerting configs might need to be updated. |
ParkAPI (Parkplätze und Fahrradabstellanlagen)▶
Dokumentation der ParkAPI .
| 2025-10-21 | ParkAPI 0.35.0: with new restriction system, deprecating capacity_{audience} and restricted_to fields |
| 2025-07-29 | ParkAPI 0.28.0: From admin management perspective, this release is breaking, as the endpoint for generic uploads changes from /api/admin/v1/generic-parking-sites to /api/admin/v1/generic. Data consumers do not experience any breaking changes. |
| 2025-02-25 | ParkAPI 0.20.0: with a new, abstract Datex II approach. This means that expected config values for vrs_* converters have to be converted to the new, abstract format. If you don't use VRS converters, no change is necessary. |
| 2024-09-03 | ParkAPI 0.12.0 with using BFRK API. If you used the bfrk converters before, please make sure that you update your config. |
| 2024-08-20 | ParkAPI 0.10.0 with Kienzler SplitUp. If you used the kienzler converter before, please make sure that you update your config. |
OCPDB (E-Ladesäulen)▶
Dokumentation der OCPDB.
| 2025-05-20 | OCPDB 2.0:
|
| 2025-01-28 | OCPDB 1.3: Mitigate OCPI compatibility issues
The OCPDB changes might have effects on clients, as it changes the type of id from integer (which was wrong) to string in OCPDBs public JSON output, and creates a clear logic how to name upstream field identifiers. More details on that can be found at the issue. The OCPI changes also introduce a new strict mode: with ?strict=true, you will get OCPI objects without additional attributes. |
GTFS-API (Soll-Fahrplandaten)▶
Dokumentation der GTFS-API.
| 2025-10-28 | gtfs-importer: upgraded postgis-gtfs-importer to v5-2025-10-22T10.41.11-588c98b – If you have not disabled the GTFS tidying (using GTFSTIDY_BEFORE_IMPORT=false), gtfsclean (a fork) will now be used instead of gtfstidy |
| 2025-02-25 | gtfs-importer: upgraded postgis-gtfs-importer to v5-2025-02-19T00.49.01-20c1b09 – This is a breaking change because future GTFS imports won't work without a manual migration step. Please run docker compose --env-file .env --env-file .env.local exec gtfs-db /bin/sh -c 'env PGUSER="$POSTGRES_USER" PGPASSWORD="$POSTGRES_PASSWORD" psql gtfs_importer -1 -c "CREATE TABLE IF NOT EXISTS latest_successful_imports (db_name TEXT PRIMARY KEY, imported_at INTEGER NOT NULL, feed_digest TEXT NOT NULL); INSERT INTO latest_successful_imports (db_name, imported_at, feed_digest) SELECT db_name, split_part(db_name, '\''_'\'', 2)::integer AS imported_at, split_part(db_name, '\''_'\'', 3) AS feed_digest FROM latest_import"' to adapt the gtfs_importer database to the new way postgis-gtfs-importer keeps track of the imports (a table latest_successful_imports). |
| 2024-10-30 | gtfs-importer: upgraded postgis-gtfs-importer to v4-2024-10-24T17.43.02-76b148e – This is a breaking change because it switches the GTFS import back (from keeping all of them) to retaining only 2 databases, similar to the old (2024-09-17) behaviour of keeping only the most recent ones. |
| 2024-07-09 | In the GTFS API (/gtfs), all geography-based columns have been changed from a hex encoding of the PostGIS-specific binary representation to GeoJSON. If you depend on the current format of shape_pt_loc in /gtfs/shapes or stop_loc in /gtfs/stops, you will have to adapt your code. For example, the stop_loc format of stop de:08231:50_Parent (Pforzheim Hauptbahnhof) changes from "0101000020E6100000D28BDAFD2A68214003098A1F63724840" to {"type":"Point","coordinates":[8.703453,48.89365]}. |
GeoServer (WMS/WFS/WMTS/WCS)▶
Einstiegsseite des GeoServer.
| 2025-12-11 | MobiData-BW:park-api_car, MobiData-BW:park-api_car_lines, MobiData-BW:park-api_car_polygons: rename all fields including woman to women, for instance capacity_woman to capacity_women |
| 2025-08-22 | MobiData-BW:sharing_stations: change name from num_scooters_standing_available to num_scooters_available |