standard public schema
Contains the association, if any, between a particular date and the corresponding day type. Generally this association overrides any other association possibly evaluated by the software
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | dtyp | integer | |
| * | day | integer | The date associated to the day type, specified in numerical format with the pattern yyyymmdd; unit: N.A. |
| Indexes | |||
| day2dtyp_pkey | ON day | ||
| Foreign Keys | |||
| day2dtyp_dtyp_fkey | (dtyp) → public.dtyp(idno) | ||
| Constraints | |||
| day2dtyp_day_check | ((day >= 19000101) AND (day <= 21000101)) | ||
Master table enumerating possible day types. A day type is a list of DVAL (day validities)
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | idno | integer | Surrogate primary key, usually generated in VISUM; Unit: N.A. |
| name | varchar(255) DEFAULT NULL::character varying | Human readable name of the day type; unit: N.A.; possible values: N.A.; example: "Working day" | |
| wght | double precision DEFAULT 1 | The weight of the day type, used for aggregating results for a time analysis, such as for one year. Unit: N.A.; Possible Values: wght>0 | |
| * | equilibrium_computed | boolean DEFAULT false | Indicates if an offline assignment has been executed for this day type. Populated and used only by TRE; Unit: N.A.; Possible Values: TRUE=if an offline assignment was ever executed for the day type, FALSE (NULL)=otherwise |
| reference_equilibrium_dtyp | integer | If the current record has equilibrium_computed=FALSE (NULL), then reference_equilibrium_dtyp contains the idno of another dtyp with equilibrium_computed=TRUE that is logically associated with the current day type. It is consumed by TRE online assignment and is populated by means of the TS calendar manager; Unit: N.A. | |
| Indexes | |||
| dtyp_pkey | ON idno | ||
| Foreign Keys | |||
| dtyp_reference_equilibrium_dtyp_fkey | (reference_equilibrium_dtyp) → public.dtyp(idno) | ||
| Referring Foreign Keys | |||
| day2dtyp_dtyp_fkey | (idno) ← public.day2dtyp(dtyp) | ||
| dtyp_reference_equilibrium_dtyp_fkey | (idno) ← public.dtyp(reference_equilibrium_dtyp) | ||
| dtyv_dtyp_fkey | (idno) ← public.dtyv(dtyp) | ||
| lab_days_idno_fkey | (idno) ← public.lab_days | ||
| simu_dtyp_fkey | (idno) ← public.simu(dtyp) | ||
| tsta_base_dtyp_fkey | (idno) ← public.tsta_base(dtyp) | ||
| Constraints | |||
| dtyp_wght_check | (wght >= (0)::double precision) | ||
Table to express couples of DTYP and DVAL. A DTYP is constituted as a set of DVALs. Each DVAL can anyhow be used by more than one DTYP
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | dtyp | integer | |
| * | dval | integer | |
| Indexes | |||
| dtyv_pkey | ON dtyp, dval | ||
| Foreign Keys | |||
| dtyv_dtyp_fkey | (dtyp) → public.dtyp(idno) | ||
| dtyv_dval_fkey | (dval) → public.dval(idno) | ||
Stores day validities, usually defined in the model. DVAL is the master table storing sets of days. The child table DVEL specifies the content of the set
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | idno | integer | Surrogate primary key, usually generated in VISUM; Unit: N.A.; Possible Values: 0 for the predefined "always" set of days, -1 for the predefined "never" set of days |
| name | varchar(255) DEFAULT NULL::character varying | Descriptive name of the set of days; Unit: N.A.; Possible Values: N.A.; Example: "never", "always", "working days" | |
| excl | integer DEFAULT 0 | Validity by exclusion; Unit: N.A.; Possible Values: 0 if the record childs specify all the days in the set, 1 if the record childs specify all the days not in the set; | |
| wght | double precision DEFAULT 1 | The weight of the set of days, represented as a positive number. A day could be associated with two different day types (with different weights). In this case, the day is automatically associated with the one with the highest weight; Unit: N.A.; Possible Values: >0 | |
| fday | integer | Contains the first day of the set. The value is specified in numerical format with the pattern yyyymmdd. NULL means no lower limit; Unit: N.A. | |
| lday | integer | Contains the last day of the set, specified in numerical format with the pattern yyyymmdd. NULL means no upper limit; Unit: N.A. | |
| Indexes | |||
| dval_pkey | ON idno | ||
| Referring Foreign Keys | |||
| dseg_dval_fkey | (idno) ← public.dseg(dval) | ||
| dtyv_dval_fkey | (idno) ← public.dtyv(dval) | ||
| dvel_dval_fkey | (idno) ← public.dvel(dval) | ||
| line_route_dval_fkey | (idno) ← public.line_route(dval) | ||
| link_dval_fkey | (idno) ← public.link(dval) | ||
| mtur_dval_fkey | (idno) ← public.mtur(dval) | ||
| runs_dval_fkey | (idno) ← public.runs(dval) | ||
| stat_dval_fkey | (idno) ← public.stat(dval) | ||
| stop_dval_fkey | (idno) ← public.stop(dval) | ||
| tatt_dval_fkey | (idno) ← public.tatt(dval) | ||
| ttab_dval_fkey | (idno) ← public.ttab(dval) | ||
| turn_dval_fkey | (idno) ← public.turn(dval) | ||
| Constraints | |||
| dval_excl_check | ((excl = 0) OR (excl = 1)) | ||
| dval_fday_check | ((fday >= 19000101) AND (fday <= 21000101)) | ||
| dval_lday_check | ((lday >= 19000101) AND (lday <= 21000101)) | ||
Stores day validity elements, usually defined in the model. DVEL is the child table of the DVAL table, used to specify sets of days to be aggregated in a DVAL set
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | dval | integer | |
| * | iele | integer | Day validity element index. A DVAL can contain multiple DVEL, the order of the DVELs is specified here; unit: n.a. |
| dawe | varchar(255) DEFAULT NULL::character varying | Days of the week, represented as a string of length 7. Each nth character can be Y/N, representing that the nth day of the week (starting from Sunday) is included (Y) or excluded (N); Unit: N.A.; Possible Values: NULL=The whole week, ""=The whole week, any string of Ys and Ns of length 7; Example: "YYNNYYY" | |
| damo | varchar(255) DEFAULT NULL::character varying | Days of the month, represented as a string of length 31. Each nth character can be Y/N, representing that the nth day of the month is included (Y) or excluded (N); Unit: N.A.; Possible Values: NULL=The whole month, ""=The whole month, any string of Ys and Ns of length 31 | |
| wemo | varchar(255) DEFAULT NULL::character varying | Weeks of the month, represented as a string of length 5. Each nth character can be Y/N, representing that the nth week of the month is included (Y) or excluded (N); Unit: N.A.; Possible Values: NULL=The whole month, ""=The whole month, any string of Ys and Ns of length 5; Example: "YYYNY" | |
| weye | varchar(255) DEFAULT NULL::character varying | Week of the year, represented as a string of length 53. Each nth character can be Y/N, representing that the nth week of the year is included (Y) or excluded (N); Unit: N.A.; Possible Values: NULL=The whole year, ""=The whole year, any string of Ys and Ns of length 53 | |
| moye | varchar(255) DEFAULT NULL::character varying | Month of the year, represented as a string of length 12. Each nth character can be Y/N, representing that the nth month of the year is included (Y) or excluded (N); Unit: N.A.; Possible Values: NULL=The whole year, ""=The whole year, any string of Ys and Ns of length 12; Example: "YYYNYYYNNYYY" | |
| iday | integer | Initial day of the set, specified in numerical format with the pattern yyyymmdd; unit: N.A. | |
| eday | integer | End day of the set, specified in numerical format with the pattern yyyymmdd; unit: N.A. | |
| itim | integer | Initial within-day instant from which the validity element is active, expressed in numerical format through the pattern hhmmss; Unit: N.A.; Possible Values: [000000, 240000], NULL=000000 | |
| etim | integer | End within-day instant of the activity of the validity element, expressed in numerical format with the pattern hhmmss; Unit: N.A.; Possible Values: [000000, 240000], NULL=240000 | |
| Indexes | |||
| dvel_pkey | ON dval, iele | ||
| Foreign Keys | |||
| dvel_dval_fkey | (dval) → public.dval(idno) | ||
| Constraints | |||
| dvel_iday_check | ((iday >= 19000101) AND (iday <= 21000101)) | ||
| dvel_eday_check | ((eday >= 19000101) AND (eday <= 21000101)) | ||
| dvel_itim_check | ((itim >= 0) AND (itim <= 240000)) | ||
| dvel_etim_check | ((etim >= 0) AND (etim <= 240000)) | ||
Contains the range of days available for lab mode computation, useful only if Optima is set to work in lab mode
| Idx | Field Name | Data Type | Description |
|---|---|---|---|
| * | idno | integer | Surrogate primary key for this record; Unit: N.A. |
| * | dscr | varchar(255) | Human readabale description for the lab mode setting; unit: N.A. |
| * | sday | integer | Simulation day. The value is specified in numerical format with the pattern yyyymmdd. NULL means no lower limit; unit: N.A. |
| * | init | integer | Simulation start time, expressed in numerical format with the pattern hhmmss; Unit: N.A.; Possible Values: [000000, 240000], NULL=000000 |
| * | ends | integer | Simulation end time, expressed in numerical format with the pattern hhmmss; Unit: N.A.; Possible Values: [000000, 240000], NULL=000000 |
| Indexes | |||
| lab_days_pkey | ON idno | ||
| Foreign Keys | |||
| lab_days_idno_fkey | (idno) → public.dtyp | ||
| Constraints | |||
| lab_days_sday_check | ((sday >= 19000101) AND (sday <= 21000101)) | ||
| lab_days_init_check | ((init >= 0) AND (init <= 240000)) | ||
| lab_days_ends_check | ((ends >= 0) AND (ends <= 240000)) | ||