You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main export format of hermes will be a GTFS format. All other exports will be based on the transformation of exported GTFS package then.
The most important automation in Hermes is schedule tables export. That means we need to implement a mechanism of creating schedules tables from GTFS. These reports are published on bus stops in a paper form then.
Some basic requirements:
Input: gtfs zipped package
Output: pdf or any editable open doc format (docx / odt etc.)
Schedule templates must be separatable from generation code, i.e. when a new schedule design comes, we will be able to update generator will minimal effort
Ideally - have such templating mechanism they can handle by their own, i.e. they will be able to edit templates and import them to the generator.
I heard about JasperReports from Java world. It even has IDE for creating reports incl document templates. There is a python binding https://github.com/jadsonbr/pyreport. Im not sure if it's a right tool for this task, research needed.
The main export format of hermes will be a GTFS format. All other exports will be based on the transformation of exported GTFS package then.
The most important automation in Hermes is schedule tables export. That means we need to implement a mechanism of creating schedules tables from GTFS. These reports are published on bus stops in a paper form then.
Some basic requirements:
I heard about JasperReports from Java world. It even has IDE for creating reports incl document templates. There is a python binding https://github.com/jadsonbr/pyreport. Im not sure if it's a right tool for this task, research needed.
Some milestones:
The text was updated successfully, but these errors were encountered: