Introduction
Documentation
Syntax
|
|
| Documentation
|
child element summarizing the pantograph energy parameters
|
| Subschema
|
infrastructure
|
| Parents*
|
electrificationSection
|
| Children
|
None
|
Attributes:
- compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional;
tTSIPantoHeadTypeList),
- contactStripMaterials: space separated list of permitted contact strip materials (optional;
tContactStripMaterialList),
- nationalPanHeadTypes: space separated list of accepted other pantograph heads (optional;
tPantoHeadTypeList),
- requiresTSIcompliance: flag, whether a TSI complaint pantograph head is required (optional;
xs:boolean)
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
|
|
| Documentation
|
child element summarizing the pantograph energy parameters
|
| Subschema
|
infrastructure
|
| Parents*
|
electrificationSection
|
| Children
|
None
|
Attributes:
- compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional;
tTSIPantoHeadTypeList),
- contactStripMaterials: space separated list of permitted contact strip materials (optional;
tContactStripMaterialList),
- nationalPanHeadTypes: space separated list of accepted other pantograph heads (optional;
tPantoHeadTypeList),
- requiresTSIcompliance: flag, whether a TSI complaint pantograph head is required (optional;
xs:boolean)
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
|
|
| Documentation
|
child element summarizing the pantograph energy parameters
|
| Subschema
|
infrastructure
|
| Parents*
|
electrificationSection
|
| Children
|
None
|
Attributes:
- requiresTSIcompliance: flag, whether a TSI complaint pantograph head is required (optional;
xs:boolean),
- compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional;
tTSIPantoHeadTypeList),
- nationalPanHeadTypes: space separated list of accepted other pantograph heads (optional;
tPantoHeadTypeList),
- contactStripMaterials: space separated list of permitted contact strip materials (optional;
tContactStripMaterialList)
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The attributes have been changed.
Semantics
Best Practice / Examples
This example is based on ERA knowledge graph (external link)[1][2][3][4].
<infrastructure id="is_01">
<topology>
<netElements>
<netElement id="ne_a11">
<elementCollectionUnordered id="ne_a11_ecu01">
<elementPart ref="ne_a01"/>
</elementCollectionUnordered>
</netElement>
</netElements>
</topology>
<functionalInfrastructure>
<electrificationSections>
<electrificationSection id="es01">
<energyPantograph contactStripMaterials="copper"/>
<linearLocation id="es01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="ne_a01" keepsOrientation="true"/>
</linearLocation>
</electrificationSection>
</electrificationSections>
<lines>
<line id="lineSection1" >
<name name="Žrnovac-Skrad" language="hr"/>
<linearLocation id="lin01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="ne_a11" keepsOrientation="true"/>
</linearLocation>
<beginsInOP ref="opp01"/>
<endsInOP ref="opp02"/>
</line>
</lines>
<operationalPoints>
<operationalPoint id="opp01">
<name name="Žrnovac" language="hr"/>
<connectedToLine ref="lineSection1"/>
</operationalPoint>
<operationalPoint id="opp02">
<name name="Skrad" language="hr"/>
<connectedToLine ref="lineSection1"/>
</operationalPoint>
</operationalPoints>
<tracks>
<track id="tr01" type="mainTrack">
<linearLocation id="tr01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="ne_a01" keepsOrientation="true"/>
</linearLocation>
</track>
</tracks>
</functionalInfrastructure>
</infrastructure>
Additional Information
Notes
Additional Information
| 🗒️
|
This segment provides background information that is not relevant for the certification process.
|
|
|
Example was reviewed by the coordinator (link to the railML® website) of the Infrastructure subschema on 2025-11-11.
Open Issues
References