fluctuo/gbfs-issues

gbfs-issues's Issues

Blocked User-Agent on Link feeds

MobilityData/gbfs-validator#90

They block the default Got's User-Agent

Wrong current_fuel_percent for Nextbike / Bergisches

The value for current_fuel_percent on Nextbike / Bergisches (https://gbfs.nextbike.net/maps/gbfs/v2/nextbike_ac/de/free_bike_status.json) is invalid.

This value represents the current percentage, expressed from 0 to 1, of fuel or battery power remaining in the vehicle.

On the feed, it's between 0 and 100

Hopr | Geometry type "Polygon" instead of "MultiPolygon"

In https://gbfs.hopr.city/api/gbfs/27/geofencing_zones the geometry is a "Polygon" instead of "MultiPolygon"

https://github.com/MobilityData/gbfs/blob/v2.2/gbfs.md#geofencing_zonesjson-added-in-v21

- geometry | Yes | GeoJSON Multipolygon

Helbiz wrong current_range_meters

On Helbiz free_bike_status, the current_range_meters seem in kilometers instead of meters
Documentation (https://github.com/MobilityData/gbfs/blob/master/gbfs.md#vehicle_statusjson) said

This value represents the furthest distance in meters that the vehicle can travel with the vehicle's current charge [...]

See https://gbfs.helbiz.com/v2.2/rome/free_bike_status.json

{
    "bike_id": "867584033465480",
    "lat": 41.837751,
    "lon": 12.454576,
    "is_reserved": false,
    "is_disabled": true,
    "vehicle_type_id": "scooter",
    "rental_uris": {
        "android": "https://deeplink.helbiz.com/startRide?code=A0U7",
        "ios": "https://deeplink.helbiz.com/startRide?code=A0U7"
    },
    "last_reported": 1677070734,
    "current_range_meters": 9.45,
    "pricing_plan_id": "price_scooter"
}

current_range_meters must be 9450

Invalid station on Lime / Paris

Lime / Paris return a strange and unique station https://data.lime.bike/api/partners/v2/gbfs/paris/station_status

{
    "station_id": "paris",
    "num_bikes_available": 14748,
    "num_docks_available": 999999,
    "is_installed": true,
    "is_renting": true,
    "is_returning": true,
    "last_reported": 1684834620
}

I'm not sure, this "station" should exist

https://gbfs-validator.netlify.app/?url=https%3A%2F%2Fdata.lime.bike%2Fapi%2Fpartners%2Fv2%2Fgbfs%2Fparis%2Fgbfs.json

Missing `station_status.json` on flammingo

Actually, it is probably better to remove the station_information.json files, as "stations" are used for parking

Velib is not accessible from datacenter ips

The velib feed (https://velib-metropole-opendata.smoove.pro/opendata/Velib_Metropole/gbfs.json) is not accessible from datacenters

It highly prevents the reuse, and it is not to valid it thought the gbfs-validator

Flammingo | Invalid geometry's names

On the geofencing_zones they use the v3.0 format for name
https://data.rideflamingo.com/gbfs/wellington/geofencing_zones.json

{
  "properties": {
    "name": [
      {
        "text": "Wellington Botanic Gardens",
        "language": "en"
      }
    ],
    "rules": [...]
  }
}

It should be

{
  "properties": {
    "name": "Wellington Botanic Gardens",
    "rules": [...]
  }
}

on this version