App to automate wheelchair status csv generation for AMO (assisted mobility) #24
Description
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):
Elevator Pitch:
- 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
- See illutration at the beginning.
- See xlsx with the calculations.
- Simple webapp, potentially running on the SKI ATLAS cloud platform.
- One or two views/forms where I can submit the yearly timetable in the form a zipped HRDF file or maybe even choose the file directly from https://opentransportdata.swiss/en/dataset/timetable-54-2022-hrdf as well as the DiDok exports https://opentransportdata.swiss/en/dataset/didok and https://opentransportdata.swiss/en/dataset/prm_data/resource/84b57520-d3d3-4657-8057-c007b884e8de.
- Calculation rules according to the requirement document.
- Output is a zipped package of four csv files as depicted in the illustration at the top (one csv is constant) that is uploaded to the opentransportdata ftp.
- Some form of error handling that we will have to discuss.
- TODO
Kind regards,
Adrian