public-transport / db-hafas Goto Github PK

Version 1.2.1 of hafas-client just got published.

This version is covered by your current version range and after updating it in your project the build failed.

hafas-client is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

How can we identify / reference a route by id?

Version 1.10.0 of db-stations just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As db-stations is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

pricing information would be a nice-to-have feature

GET http://open-api.bahn.de/bin/rest.exe/location.name?authKey=&format=json

This returns neither a valid JSON error description nor a non-200 HTTP status code. This makes it really hard to programmatically distinguish valid responses from errors.

Version 1.21.0 of db-stations was just published.

This version is covered by your current version range and after updating it in your project the build failed.

db-stations is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.20.0 of db-stations was just published.

This version is covered by your current version range and after updating it in your project the build failed.

db-stations is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.12.0 of db-stations just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As db-stations is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

When getting a route from Heilbronn -> Westerland(Sylt) (hafas.journeys("8000157", "8006369"))

Hamburg-Altona has the evaId 8002553 but we expect 8098553, because 8098553 is marked as isMain in StaDa

First of all, thank you for this nice API!

I discovered that the results option parameter for the stationsNearby search has no effect (at least for the cases that I tested). It does not matter if I pass in 1, 5, or 10 -- the API always delivers more stations.

For example, hafas.nearby( 50.967417, 11.031457 ) gives me 33 results, where as the documentation states that 8 should be the default value for the results parameter. hafas.nearby( 50.967417, 11.031457, { results: 5 } ) yields the same amount of stations.

mode, public, operator art not available in Journey.Leg as defined in 1.2.0

They are available in Journey.Leg.line

🇩🇪 » Wenn ein Journey ein ICE beinhaltet, besitzt dieser Zug einen AdminCode. DIeser kann unter depature > line > adminCode gefunden werden. In meinem Beispiel ist der AdminCode '80___' für den ICE 502. Nach meiner Anfrage fährt dieser über Berlin Hbf und endet in Hamburg-Altona. Was bringt mir dieser Code und wofür kann dieser genutzt werden.

🇬🇧 » When a journey contains a National Express (ICE) I get a admincode for the train from departure > line > adminCode. In my case the adminCode is '80___' for the ICE 502. In my request the train goes via Berlin Central to Hamburg-Altona. What are use cases for the code?

{
origin: {
type: 'stop',
id: '8011160',
name: 'Berlin Hbf',
location: {
type: 'location',
id: '8011160',
latitude: 52.524924,
longitude: 13.369629
},
products: {
nationalExpress: true,
national: true,
regionalExp: true,
regional: true,
suburban: true,
bus: true,
ferry: false,
subway: true,
tram: true,
taxi: false
}
},
destination: {
type: 'stop',
id: '8002549',
name: 'Hamburg Hbf',
location: {
type: 'location',
id: '8002549',
latitude: 53.553533,
longitude: 10.00636
},
products: {
nationalExpress: true,
national: true,
regionalExp: true,
regional: true,
suburban: true,
bus: true,
ferry: false,
subway: true,
tram: false,
taxi: false
}
},
departure: '2021-12-22T21:56:00+01:00',
plannedDeparture: '2021-12-22T21:38:00+01:00',
departureDelay: 1080,
arrival: '2021-12-22T23:48:00+01:00',
plannedArrival: '2021-12-22T23:33:00+01:00',
arrivalDelay: 900,
reachable: true,
tripId: '1|1079723|0|81|22122021',
line: {
type: 'line',
id: 'ice-502',
fahrtNr: '502',
name: 'ICE 502',
public: true,
adminCode: '80____',
productName: 'ICE',
mode: 'train',
product: 'nationalExpress',
operator: {
type: 'operator',
id: 'db-fernverkehr-ag',
name: 'DB Fernverkehr AG'
}
},
direction: 'Hamburg-Altona',
currentLocation: { type: 'location', latitude: 52.497651, longitude: 13.372785 },
arrivalPlatform: '5',
plannedArrivalPlatform: '5',
departurePlatform: '14',
plannedDeparturePlatform: '14',
loadFactor: 'low-to-medium'
}

Since July2020 there is major change in train schedule - at least between Freiburg and Basel but it is not updated in db-hafas api. I am using this one in magicmirror module "MMM-PublicTransportHafas" by raywo. How can I update this to the latest plan? If not possible, are there any other alternatives?

Thanks

Version 1.13.0 of db-stations just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As db-stations is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The DB API exposes stations like BERLIN, which are actually "clusters" of all stations in Berlin. Use the clustering feature discussed in public-transport/friendly-public-transport-format#7 once it is specified.

@juliuste said he has an idea on how to automatically identify them.

Hello,

as discussed here:

https://forum.iobroker.net/topic/35169/test-adapter-fahrplan-v0-1-x-github-alpha-version/21

I have the following journey:

Provider: DB
From: 8002334
To: 8000107
Options: {"results":3,"language":"de","remarks":true,"transfers":0,"products":{"suburban":true}}

So I should only get connections without transfer and products suburban.

But there appears one connection in the early morning (4:xx) with 1 change and product Bus frequently.

Thanks and regards,

Ralf

I've been curious to watch the path of ICE trains through Germany and have noticed that they disappear or don't match timetables at all.
For instance, the Hamburg-Munich services depart Hamburg-Altona north and then take the curve towards Sternschanze, disappearing from the data feed once they pass the station.
Is there any chance to be able to watch the full path of these trains?

Is all of the underlying Hafas Api free to use ? I can't find their Terms of Use.

Let's use db-clean-station-name to get nice station names.

Version 1.2.0 of hafas-client just got published.

This version is covered by your current version range and after updating it in your project the build failed.

hafas-client is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴