When did the bus actually called at a stop? about open-bus HOT 7 CLOSED

So, good news.
We have a few days of data for the stops of three bus lines:

• 19 in Jerusalem (from Ein Karem to Har Hazofim) - 40 stops
• 480 from Jerusalem to Tel-Aviv - 3 stops
• 947 from Haifa to Jerusalem - 29 stops

Because we poll stops (not lines) we also have data for all other buses that stop at the same stops.

The data is accessible through re:dash, in the arrivals table (edit: table renamed to siri_arrivals).

The fields of the table aren't self explanatory,
so you may need to read the doc. If you do, how about summarising the relevant parts for everyone else?

We also need to start looking the the data. Does it make sense at all? There may be problems with the script the fetches the data and inserts to the db...

from open-bus.

Hi,
I made a short description of what I could make of the tables that we got from siri.
From what I understand that's not all tables. Is there somewhere I could get at least the names of the tables available? I quickly scanned the doc, but it's more about the connection between different parts of the process and not about what's available there.

https://docs.google.com/spreadsheets/d/1Hi2DvVzpz_LVUMEBZ0qMOxp4jyXcRF4jlojK5Uioey8/edit?usp=sharing

from open-bus.

@OrLichter ,
The only tables coming from Siri are arrivals & responses.
Response is the unprocessed xml. Arrivals is the the parsed response.
You can see the script that generated them here: https://github.com/hasadna/open-bus/blob/master/siri/fetch_and_store_arrivals.py

The rest of the tables are less relevant at for this task I think. They mostly have to do with the static (planning) data (GTFS).

I made a list of the tables and what they are about here.

from open-bus.

Amir Carmel of the MoT suggested a method for finding bus locations. I am not posting it here because GitHub masses up RTL, but it's available on the mailing list here:

https://groups.google.com/forum/#!topic/openbus-israel/KC60TZu1GyI

I haven't made much effort to understand what he is suggesting. It does seem to me that it might require keeping polling other information than what we currently have in the DB.

Edit: Amir's mail talks about the VehiceLocation field. This field should contain the bus exact location (coordinate). However it's an optional field and we don't receive it. I have written to Amir asking clarifications about that. If we can receive this field this task will become much much easier.

from open-bus.

Good news: apparently there are some extra fields in the SIRI reply that we haven't been keeping in the past.

In particular vehicle_ref is the license number of the bus! This should make tracking the buses much easier.

Can anyone (@OrLichter? @efratoio?) have a look at the problem again and see if it's now more feasible?

Notes:

• I changed the relevant database tables. The main table is now called siri_arrivals. (There's also siri_raw_response that contains the original XML)
• I wrote documentation about SIRI. I hope it's more readable than the PDFs supplied by the MOT.

from open-bus.

This issue isn't up to date with the newest development.
I am closing this and will create new more relevant issues.

from open-bus.

Closing for now, will submit new up to date issue.

from open-bus.