This contains the implementation of support for the OV-chipkaart used in the Netherlands.
The database is created with ovc-tools, specifically my fork of it (nothing special just updated data and an option to discard machines data).
To fully read an OV-chipkaart you will need the keys for all the sectors. These keys can be obtained with mfocGUI and can be found in the Keys folder after dumping. If you want to save some time, you could dump only the so called 'A' keys as those are the only ones that are used ;).
-
Normally every trip has an end time (ExitTimeStamp) and it would be nice if it would be displayed.
-
Most trips have a start and an end station, but some of the names are too long to display them (both) on the same line. Split them into two lines and maybe display the start or end time behind each one?
-
Display the subscriptions somewhere (its own tab or Advanced Info for example).
-
The whole keys part could use a serious rewrite...
-
Maybe move the database outside of the app to save space for those who don't need it?
-
See all the TODOs and FIXMEs throughout the code for everything that needs fixing.
-
(Not OV-chipkaart related and for the future): display public transit lanes on the Google map (if available)?
- PC Active for hosting the wiki.
- OV-Chipkaart Forum for all the research and information.
- Huuf for mfocGUI.
- Nexus-s-ovc which got me started.
- Eric Butler for FareBot of course ;)