dbopendata db-fahrplan-api issues

dbopendata / db-fahrplan-api

DB Fahrplan API

31 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Is this offline?

#36 danieljuschus opened 8 months ago
0
JourneyDetail Links broken

#35 Aimmig opened 4 years ago
0
Departures and arrivals for stations return no trains

#34 DaleSchultz opened 4 years ago
0
Internal server error when searching for Wuppertal Hbf

#33 McToel opened 4 years ago
6
Missing Station

#32 technik-kvz opened 5 years ago
0
StationBoard not available

#31 MrKrisKrisu opened 6 years ago
1
Illegal character in attribute name

#30 jvf opened 7 years ago
0
JSON objects returned from open-api.bahn.de are not RFC 4627 compliant

#29 nekrondev opened 7 years ago
0
Real time data and local traffic

#28 choallin opened 7 years ago
0
departureBoard returns error for requests later than 2016-12-10

#27 J0ANMM opened 7 years ago
1
location.name service doesn't find "Rösrath"

#26 marians opened 8 years ago
3
Documentation on the ref parameter and journeyDetail endpoint in general

#25 alios closed 8 years ago
3
-

#24 Stefan-Hintz closed 8 years ago
1
Add missing parameter 'direction' to departure and arrival board

#23 dredav opened 8 years ago
0
DepartureBoard or ArrivalBoard returns wrong protocol version in journeyRef

#22 JNK closed 8 years ago
1
add connection search from station to station

#21 maltegoetz opened 8 years ago
9
Consider "destination" in the departureBoard operation

#20 highsource opened 8 years ago
0
Build a location.coordinate service to query stations in the near of latitude,longitude

#19 highsource opened 8 years ago
0
Why is Donaueschingen (and other stations) found for "düs"

#18 highsource opened 8 years ago
1
location.name operation should indicate that not all of the requests were returned

#17 highsource opened 8 years ago
1
Request of departure board with destination contains departures with journeys not to this destination

#16 highsource opened 8 years ago
0
Use the same protocol in the JourneyDetailRef as in the ArrivalBoard or DepartureBoard request

#15 highsource opened 8 years ago
0
Typo in departure response

#14 marcelbuesing opened 8 years ago
11
Favor empty array over error when retrieving departures

#13 marcelbuesing opened 8 years ago
4
JourneyDetail Parser Error Response

#12 marcelbuesing opened 8 years ago
1
Provide prices/fares for each leg

#11 J0ANMM opened 8 years ago
1
Improper formatted JourneyDetailRef url

#10 marcelbuesing closed 8 years ago
5
Show delay times

#9 thekonz opened 8 years ago
6
Use correct types in JSON

#8 highsource opened 8 years ago
1
Output lists of elements ALWAYS as array, regardless whether it is one element or many

#7 highsource opened 8 years ago
4
Output arrays without intermediate object in JSON

#6 highsource opened 8 years ago
1
StopLocation.name should allow more than 50 characters

#5 highsource opened 8 years ago
0
Add StopLocation.type

#4 highsource opened 8 years ago
0
Use the same format of the stop ids in location.name and other operations

#3 highsource opened 8 years ago
0
Provide dates/times in local time zone as well as UTC

#2 highsource opened 8 years ago
0
Enable cross-origin resource sharing

#1 highsource opened 8 years ago
4