QSI-import: extensions SonRoad18 (table "road")
A preliminary QSI-extension [version: 2025.07.08a]
| This document shortly and informally describes a (preliminary) QSI-extension currently implemented in SLIP'25. This extension can be used to import road-descriptions that are convenient for working with SonRoad18. | ❑ | Notes: - To keep this draft document simple, several semantic-aspects are only partly specified.
- The below description does not mention fields that are, according to the standard QSI specifications, mandatory in all tables for all element types: fields NAME, ID must always be present. Fields not described in this standard are listed here as "new".
- For now, fields "SLOPE" and "SLOPE_VAL" are ignored in SLIP (the value of field SLOPE is assumed to be always true, which in QSI means "calculate slope from geometry"; in the current version, the user is expected to ensure that the appropriate slope-setting is used when importing a QSI-project; see calculation options).
- The here described schemas are likely to be modified in the future.
|
|
Definitions in the QSI-index – entries in file .QSI The index file (.QSI) should contain, in section "Metadata", an entry that specifies the model to use for the roads (e.g., "SONR18", "STL"). Example:
[Metadata]
fmtroad=SONR18 |
Optionally, a format-specification can be included using the standard entry fmtqsi (currently ignored).
Variant/schema "N, N2%" (EMI_TYPE=3) – fields/attrs. in .DBF files for roads In this schema (selected at the road-element level by defining field EMI_TYPE=3), road-traffic is mainly described using N, N2%, a single v (that of automobiles) and information about the distribution of vehicle-categories within N1 and N2 (e.g., an N1N2-converter code/ID). A few other fields are used for pavement and for a few corrections.
Attributes:
- Attributes that already exist in the QSI-standard:
| Attr. | Type | Value | Comments |
| EMI_TYPE | N1 | 3 | this "3" causes M_D, P_D, V_PKW_D,... to be expected |
| V_PKW_D | N3 | v,day | in this schema, we only use "PKW" speed (v-lims. apply) |
| V_PKW_N | N3 | v,night | " |
| M_D | N5 | N,day |
| P_D | N5.1 | N2%,day |
| M_N | N5 | N,night |
| P_N | N5.1 | N2%,night |
| SCS | N4.1 | dist. between the outer lanes | when field WIDTH is absent/empty but the value of SCS is provided, this value plus 3.5m is used to define the road-width (see field WIDTH below); for now, this is the only use of this field's value in SLIP |
| ❑ | Notes: - Other speed-fields (e.g., V_LKW_D, V_LKW_N) must be absent, empty or contain the value that is obtained by applying vehicle-speed-limitations to V_PKW_*.
- For each day-period, the provided N and N2% are fully assigned to the source-element described by each given record.
|
- (New) attributes to improve the description of a road-traffic:
| Attr. | Type | Value | Comments |
| MDSTR_ID | C15 | code of a veh. distribution (e.g. "SS_30", "HLS_4_NU_120"; see list of all currently supported codes below) | see notes below |
| TRDIR | N2.0 | 0: bidirectional traffic (50%/50%)
+1: all traffic in poly's input-direction
-1: all traffic in opposite-to-poly's direction | optional; default: 0 (bidirectional) |
| K1 | L | true if K1 wanted | as defined in LSV, App. 3 (optional field; when the field is absent, the default is true) |
| ❑ | Notes: - MDSTR_ID contains an id corresponding to a S10-converter code; essentially, this specifies information about the distribution of S10-vehicles. This is the set of currently supported codes: { SS_30, SS_50, VS_50_60, VS_80, HVS_50_60, HVS_80, HLS_2_80, HLS_2_100, HLS_4_N_80, HLS_4_U_80, HLS_4_NU_80, HLS_4_N_100, HLS_4_U_100, HLS_4_NU_100, HLS_4_N_120, HLS_4_U_120, HLS_4_NU_120, HLS_6_N_120, HLS_6_U1_120, HLS_6_U2_120, HLS_6_NU1U2_120 }. For details on these codes, see Distribution der Fahrzeugsklassen (Swiss10-Konverter).
The values specified by M_D, P_D are expected to be honored by the importer at the record level; the provided S10-converter code only influences the proportions of vehicles within each LSV-category for the day-period. (The analogous is true for M_N, P_N.) Thus, in the case of a lane, the values specified by M_* and P_* correspond to the lane, not to the whole road. When this field is present, it always takes precedence over ROAD_TYPE (see below). - Field ROAD_TYPE (a standard QSI field) is currently ignored (and its presence is not required).
- Speed-limitations for each vehicle-category are automatically applied.
|
- (New) attributes to improve the description of the road-pavement:
| Attr. | Type | Value | Comments |
| PAV_ID | C15 | pav. ID (e.g., "KB50_0","KB50_minus1", "KB80_plus1") | see notes below |
| PAV_INLN | C140 | pav. spec. string (see examples below) | optional; when present, it takes precedence over PAV_ID; see notes below |
| K_PAV1 | N4.1 | overall pav-noise corr for LSV-cat 1 | optional; default: 0 |
| K_PAV2 | N4.1 | overall pav-noise corr for LSV-cat 2 | optional; default: 0 |
| WIDTH | N4.1 | width of the road [m]; if provided, it must be >0 | optional; when a value is provided, this definition takes precedence over field SCS (which defines the dist. between the outer lanes, and can thus be used to infer a road-width; see above); when neither WIDTH nor SCS are provided, the default value of 7.5 is used |
| ❑ | Notes: - PAV_ID should contain a "standard" pavement ID.
- PAV_INLN is an inline alternative ; the value of this field is structured as the following examples should make clear (note that the delimiter in such structured values is ';'):
| value (example) | explanation | | CPXp_50;68.2;75.1;79.6;80.5;84.9;86.1;83.8;81.5;79.9;76.8;72.7;68.8;66.8 | CPX(p) at 50km/h with the indicated spectrum (1/3-octaves);
vals. for standard CPX-freqs expected (315–5000Hz) | | DL_roll;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1;1.1 | rolling-noise-pav-corr. with the indicated spectrum (1/3-octaves);
vals. expected for 50–10000Hz |
|
- (New) attributes containing div. corrections:
| Attr. | Type | Value | Comments |
| K_OTHER | N4.1 | overall correction | optional; default: 0 |
| K_D | N4.1 | day correction | optional; default: 0 |
| K_N | N4.1 | night correction | optional; default: 0 |
- (New) attributes containing other road-properties:
| Attr. | Type | Value | Comments |
| FLOATING | L | true iff it's a floating road | optional; default: false |
Variant/schema "DTV" (EMI_TYPE=2) This schema is based on the total "DTV". It is similar to the "N, N2%" schema above but defines EMI_TYPE=2 and requires a field DTV (of type N6) instead of the fields for the hourly traffic. Notes:
- in SLIP, when using this schema, only one speed is used at this point (the one specified in field V_PWK_D).
- As for schema "N, N2%" (see above), the provided DTV is fully assigned to the source-element described by each given record (if it's a lane, the specified value is the DTV of the lane, not that of the whole road).
Variant/schema "Swiss10" (EMI_TYPE=6) – fields/attrs. in .DBF files for roads In this schema, fields M1_D, ..., M10_D, and M1_N, ..., M10_N are used for the hourly traffic of each S10-category and period. As for the "N, N2%" schema above, V_PKW_D and V_PKW_N are used (veh. speed-limitations apply). Fields for all other aspects (incl. width, pavement, div. corrections, div. road-properties, etc.) are also as above.
Attributes:
- Attributes that already exist in the QSI-standard:
| Attr. | Type | Value | Comments |
| EMI_TYPE | N1 | 6 | this "6" causes M1_D, ... and M1_N, ... to be expected |
| V_PKW_D | N3 | v,day | in this schema, we only use "PKW" speed (v-lims. apply) |
| V_PKW_N | N3 | v,night | " |
| M1_D, ..., M10_D | N7.1 | Ncat1,day, ... | number of veh. for each category (day) |
| M1_N, ..., M10_N | N7.1 | Ncat1,night, ... | number of veh. for each category (night) |
| ❑ | Notes: - The hourly-traffic fields specify only a vehicle-category—no sub-cat./type specification is possible; when these are needed, the "Swiss10+" schema should be used.
- This schema does only allow for categories 1–10 (in particular, it does not allow for trams); but see schema "Swiss10+".
- This schema does not contain field MDSTR_ID.
|
- (New) attributes to improve the description of a road-traffic: same as for schema "N, N2%" (see above), but without field MDSTR_ID.
- (New) attributes to improve the description of the road-pavement: same as for schema "N, N2%" (see above).
- (New) attributes containing div. corrections: same as for schema "N, N2%" (see above).
- (New) attributes containing other road-properties: same as for schema "N, N2%" (see above).
Variant/schema "Swiss10+, cats. 1–11" (EMI_TYPE=7) [this schema is particularly likely to evolve] This schema (EMI_TYPE=7) is similar to schema "Swiss10" (see above), but it contains the following vehicle-category-fields for the hourly traffic: M1_D, M2_D, M3A_D, M3C_D, M4_D, M5_D, M6_D, M7_D, M8_D, M9_D, M10_D, M11A_D, M11B_D, M11C_D, M11D_D, M11E_D, M11F_D, M11G1_D, M11G2_D, M11G3_D, M11G4_D, and the homologous fields for the night period (whose names use '_N' instead of '_D'). (Fields for all other aspects are as for the "Swiss10" scheme presented above.)
| ❑ | Notes: - Coefficients for hybrid passenger cars (3b) are not yet available in SonRoad18, and for clarity, the corresponding fields are not yet available; for now, use fields M3A_* or M3C_*, depending on the driving mode (use cat. 3c when driving in purely electric mode).
- Fields M3B_D and M3B_N are likely to be added in a rel. near future.
- If field M3A_D is not present, field M3_D is used instead (the analogous is true for M3A_N).
|
Variant/schema "Swiss10+, cat. 12" (EMI_TYPE=8) [this schema is particularly likely to evolve] This schema (EMI_TYPE=8) Is similar to schema "Swiss10+, cats. 1–11" (see above), but
- it contains (only) vehicle-related fields for category 12 (tram): M12A_D, M12B_D, M12C_D, M12D_D, M12E_D, M12F_D, M12G_D, M12H_D, M12I_D, and the homologous fields for the night period (whose names use '_N' instead of '_D');
- it contains a field called K2 (boolean; default: true) for the corresponding correction;
- field K1 and all pav-related fields are ignored.