Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App to automate wheelchair status csv generation for AMO (assisted mobility) #24

Open
haeckerbaer opened this issue May 25, 2022 · 0 comments
Assignees
Labels

Comments

@haeckerbaer
Copy link

haeckerbaer commented May 25, 2022

Hi @vasile
Draft issue to discuss requirements with you. Will update in the following weeks.

Rough sketch of how the automated generation should look (or rather my notes/thoughts):
MVP_wheelchair_status_BfR_csv_approach

Elevator Pitch:
chrome_ExAs1Yf2vL

  • Roughly 80% of the journeys according to the yearly timetable have a so called "wheelchair status" (highlighted in the screenshot) of "Unknown" which means neither the operators of assisted mobility nor the customers themselves have any information on the accessibility of the interchanges and journeys.
  • In the SKI system DiDok stop inventory of assets for accessibility data ("Bestandesaufnahme BehiG") we already have some of the data that is needed to calculate this wheelchair status for local public transport (basically for all vehicle modes except rail).
  • Combined with the yearly timetable (integrated by SKI system INFO+) we are able to calculate the "planned" and rudimentary wheelchair status according to a set of known rules for 20-60% of the journeys according to the yearly timetable.

State:
I did a proof of concept with VBZ (local public transport zurich) already:

  • I imported the yearly timetable in HRDF format into an SQL database (with your tool)
  • I exported some data into a csv by using a set of SQL queries.
  • I merged the resulting csv with various csv exports from DiDok (stop, platform and accessibility/PRM data)
  • I defined a set of rules in the form of excel functions (if, filter, lookup etc.)
  • I calculated the three csv shown in the first illustration above.
  • I am in the process of validating the results with VBZ (they already deliver such data to an SBB ftp which I use for comparison).

Next steps:

  • Next step will be to repeat this "manuall" process for the local public transport provider Bernmobil and validate the results.
  • I would like to discuss everything with you in the next weeks to get a rough estimate of how much time you would need (I assume only a few days given your expertise).
  • If we get the budget and you are interested / available I will document the requirements and we iterate over them a few times.

Roadmap:

  • Implementation optimally in 2022.Q3/4

Requirements:
TODO

Kind regards,
Adrian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants